Hard to tell. This should not be happening so it’s either a bug in movement code that we haven’t encountered yet, or it’s related to your SetNewMoveDestinationServer_Implementation. If you could share a stripped-down version of your project we could have a look and be more helpful.
Cheers,
–mieszko