---
schema_version: "1"
id: 9c4ab83196d22cc2ce6775f9a065f0d420e8741d1f1471e6422a5fb71bab49b2
title: Handle Conflicts During Optimization
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_handle_conflicts.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts_handle_conflicts.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d1530ea6aac7c1704c3caf075e699079fddd4b8b3009081e57a8f282a905ce9e
description: Define the Commit Mode in the scheduling policy to determine what happens when schedule conflicts occur during global, in-day, or resource schedule optimization.
products:
  - Field Service
release: "264"
---
# 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.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">The Agentforce Field Service and Operations core features, managed package, and mobile app are available in <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d68920e69">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d68920e69 ">To enable optimization overlaps prevention:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d68920e69 ">Custom permission set: FSL Admin Permissions</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d68920e69 ">To run Resource Schedule Optimization (RSO), in-day, or global optimization:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d68920e69 ">
              <p>One of these custom permission sets:</p>
              <ul>
                <li>FSL Admin Permissions</li>
                <li>FSL Dispatcher Permissions</li>
              </ul>
            </td>

          </tr>
        </tbody>
      </table>

![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._

The Commit Mode field in the scheduling policy determines how the system handles schedule changes made during an optimization run. For example, if a dispatcher reschedules an appointment or schedules a new job, creating discrepancies between the schedule's state at the start and completion of optimization. These changes can cause scheduling conflicts. Make sure the Commit Mode field is added to the Scheduling Policy page layout.

1. Create and manage scheduling policies from the Field Service Admin app in the Field Service settings tab. Click **Go to Guided Setup** under Getting Started, or click **New** in the Scheduling Policies tab under Scheduling.
2. Select the scheduling policy Commit Mode according to the [guidelines](https://help.salesforce.com/s/articleView?id=service.pfs_manage_opt_conflicts_guidelines.htm&type=5&language=en_US).
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_note.png)
    
    Note When you aren’t using Enhanced Scheduling and Optimization, global optimization runs in the Always Commit mode regardless of the Commit Mode setting.

#### See Also

- [Get Ready for Field Service Scheduling and Optimization](https://help.salesforce.com/s/articleView?id=service.pfs_customization.htm&release=264.0.0&type=5 "Define your service appointment lifecycle, configure appointment booking settings, and get to know your Field Service scheduling policies, optimization settings, and sharing settings.")
- [Create and Manage Field Service Scheduling Policies](https://help.salesforce.com/s/articleView?id=service.pfs_scheduling.htm&release=264.0.0&type=5 "Scheduling policies in Salesforce Field Service define the rules and objectives (scheduling priorities) for assigning work to service resources. These policies optimize resource allocation by considering factors such as resource skills, job proximity, and urgency, to make sure the right person is assigned to the right job efficiently. By considering scheduling preferences such as minimizing travel time, scheduling as early as possible, and prioritizing preferred resources, scheduling policies improve operational efficiency and customer satisfaction.")