In that case, there is a good chance that your issue relates to this rollout: Improved Mover Constraints: Enhancing Stability and Network Ownership. We recently moved into Phase 2 and you may see differences in behavior now that the default has changed.
For the time being, you can set Workspace. MoverConstraintRootBehavior to Disabled to recover the old behavior. If you would like to send me a model, I can help you work through any issues caused by the change. As the announcement post explains, this change fixes several long standing issues with mover constraints so its important that we eventually get things working with the new property enabled. Thanks.