Manage Optimization Conflicts

This is a Field Service managed package feature.

• Prevent Overlapping Field Service Optimization Requests
  When initiating resource schedule optimization, in-day optimization, or global optimization, Field Service checks for other such optimization requests that are being processed simultaneously for the same territory or service resources with at least 1 day of overlap in the optimization horizon. For example, a dispatcher activates resource schedule optimization for a resource that’s part of a dataset being optimized through in-day optimization. If an overlap is detected, a message is shown and the newly initiated optimization request is aborted. Similarly, when a dispatcher tries to make changes to the Gantt, which is being processed by a background optimization request such as in-day optimization, a message is shown notifying the dispatcher that their changes can create unwanted results. The dispatcher can choose whether to continue with the manual changes or not.
• Handle Conflicts During Optimization
  Define the Commit Mode in the scheduling policy to determine what happens when schedule conflicts occur during global, in-day, or resource schedule optimization.
• Guidelines for Using the Scheduling Policy Commit Mode
  Define what happens when a dispatcher or scheduling operation makes a change to the schedule that conflicts with an ongoing optimization process.