|
• After a dispatch process is deactivated, newly created work orders will no longer qualify for the dispatch process. Any automated scheduled or manual job run for the dispatch processes will not launch.
• It is recommended to deactivate the dispatch process when the optimization jobs are not in the Running or the In Progress status for the dispatch process. The following is the expected behavior if you deactivate a dispatch process when an optimization job is in the Running or In Progress status:
◦ Optimized Batch and Standalone Long-Term Planner Dispatch Processes: The current job in the InProgress state continues to run in the backend, and Scheduling is done successfully. The deactivation will apply only from the next scheduled job run or manually triggered run.
◦ Real-Time Optimization Dispatch Processes: The optimization job is marked IDLE immediately, and no further optimization occurs. The work orders currently undergoing scheduling are marked with the Tentative status and are not considered for scheduling after the dispatch process is activated again. To ensure that the Tentative work orders are picked for scheduling again after dispatch process activation and job initiation, you must clear some of the Work Order fields manually.
◦ Immediate Dispatch Processes: Work orders do not qualify for assignment.
|