Hi,
Yes, this happens when D365 re-evaluates resource availability during rescheduling. To avoid it:
Use “Exclusive” resource requirement on the route to ensure all jobs (setup + process) stay on the same resource
Make sure finite capacity is enabled to prevent job shifting across resources
Avoid rescheduling after the setup job has started unless needed
Confirm “Allow simultaneous execution” and resource group settings are configured properly
Let us know your scheduling method.
Regards,
Zain
Zain Mehmood
462
Moderator
Danny Bilodeau
156
Moderator
Laurens vd Tang
120
Super User 2025 Season 1