Dear Team,

The current functionality of the periodic task "Scheduling jobs" in Dynamics 365 does not retain the same resource for process-type jobs that are in an interrupted or waiting state when the associated setup job has ended. When these jobs are rescheduled, the system may assign a random resource from the resource group if multiple resources are available.

This behavior introduces significant operational challenges in real-world scenarios, as it may require setting up a different machine or physically moving WIP (Work In Progress) stock to another resource—both of which are inefficient and error-prone.

This limitation has been reported by multiple clients, particularly in environments where the route is configured with "Resource Group" as the resource requirement. Addressing this issue would greatly enhance scheduling accuracy and operational continuity.

Regards,

Prashanth T.