If another moveChunk command moves the chunk concurrently. The check for the target chunk shardId here may sometimes fail and intermittently expose a "Destination shard cannot be the same as source" error to the clients.