--- schema_version: "1" id: 9f1ba7fccb8468103e0ba0d818c5f0cd9dabb23c90c112758b804287889cc4ea title: Manage Optimization Conflicts collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/pfs_manage_opt_conflicts.md canonical_url: https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 5820ff8c2c53e1710c39b38e76f2cd90bb22128375660c992b3972f16f51a9a9 description: Enhance operational stability and reduce your optimization partial completion rate by preventing optimization conflicts when multiple optimization requests are made simultaneously on the same dataset. For example, prevent two users from creating optimization requests simultaneously for the same territory and horizon. Also configure what happens when schedule changes are made while optimization is running, for example, if a new job is automatically scheduled or a dispatcher reschedules a job while optimization is running. products: - Field Service release: "264" --- # Manage Optimization Conflicts Enhance operational stability and reduce your optimization partial completion rate by preventing optimization conflicts when multiple optimization requests are made simultaneously on the same dataset. For example, prevent two users from creating optimization requests simultaneously for the same territory and horizon. Also configure what happens when schedule changes are made while optimization is running, for example, if a new job is automatically scheduled or a dispatcher reschedules a job while optimization is running. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.
![Package icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/support_field_service/images/fs_package.png) _This is a Field Service managed package feature._ - **[Prevent Overlapping Field Service Optimization Requests](https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts_prevent_overlap.htm&release=264.0.0&type=5)** 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](https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts_handle_conflicts.htm&release=264.0.0&type=5)** 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](https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts_guidelines.htm&release=264.0.0&type=5)** Define what happens when a dispatcher or scheduling operation makes a change to the schedule that conflicts with an ongoing optimization process.