How to handle "Mismatch migrating slot" state

I have encountered situations where the controller gets into a situation where its stored state about the migration isn't what the shard node reports.
https://github.com/apache/kvrocks-controller/blob/f0af65b5725bd43b2e3ed6071d0d561e5af13bf6/controller/cluster.go#L290-L296

In this case, it isn't able to do anything and just keeps printing this message and there doesn't look like there is any API to recover from this in the controller.
Should the controller accept the migration status from the node?

This appears to happen if the node crashes immediately at the start of migration.