Conflict detection
concept australia Updated Sep 10, 2026 3 min read c_ConflictDetection.md
Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items, and planned start and end date or the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict.
Conflict detection identifies conflicts for any of the following reasons:
- The configuration items (CIs) are already scheduled at the given date and time.
- A parent or child of the CI is already scheduled at the given date and time.
- The CI is not in the maintenance window.
- A parent or child of the CI is not in the maintenance window.
- The CI is in a blackout window.
- A parent or child of the CI is in a blackout window.
- The CI is assigned to a person already scheduled at the given date and time.
Using the change.conflict.useprogressworker system property, you can manage the conflict detection process in two ways. By default, this property is set to false. Conflict detection then runs through the Change Management Worker [chg_mgt_worker] table and the Change - Conflict Detection flow (which runs as a System user).
If you set this property to true, conflict detection uses Progress Workers instead.
You can also manually execute conflict detection. For more information, see Detect conflicts manually and review conflict details.
Conflict detection process
Conflict detection can run automatically when you provide values for the Configuration item, planned start and end date fields in the change form. It can also run when any of these field values are updated. It runs as well when these field values are available and the change request state is updated.
When conflict detection identifies conflicts, it updates the conflict status and conflict last run fields. You can review conflicts in the Conflict section of the Change Request form.
Conflict detection process using flows
When the change.conflict.useprogressworker system property is set to false, conflict detection runs through the Change Management Worker [chg_mgt_worker] table and the Change - Conflict Detection flow. The flow runs as a System user. To view the associated flow, select Show Flows on the Change Request form.
Conflict Calendar
You can choose to display a conflict calendar to view identified scheduling conflicts. For more information, see Conflict calendar
- Detect change conflicts
Detect change conflicts by setting Change Management conflict analysis properties. Use the resulting information to calculate conflicts for change requests and review and modify the change to eliminate conflicts. - Create blackout and maintenance schedules in Change Management
Use the Blackout and Maintenance windows to schedule a change. Blackout windows specify times during which normal change activity should not be scheduled. Maintenance windows specify times during which change requests should be scheduled. For example, create a blackout schedule for code freezes at the end of the year. - Schedule types in conflict detection
Conflict detection uses maintenance, blackout, and information schedules to evaluate when change requests can be implemented. Each schedule type supports a category and optional ownership fields. - Configure a change request to monitor outside maintenance schedule conflicts
Configure a change request to detect conflicts outside the maintenance window. Conflict detection flags planned start and end dates that fall outside the maintenance schedule, so you can modify the change schedule accordingly. - Conflict calendar
The conflict calendar graphically represents the potential scheduling conflicts for a change request. Conflicts are identified as active change requests, blackout schedules, and changes scheduled outside maintenance schedules. Use the Scheduling Assistant to resolve any schedule conflicts. - Enable automatic change conflict detection
Automate conflict detection to run at specific intervals or when a change request is updated to immediately review the conflicts when the schedule dates are updated. - Detect conflicts manually and review conflict details
Run conflict detection manually for a change request. Review the conflicts detected either automatically or manually and resolve them by changing the schedules.
Parent Topic:Configuring Change Management
66 lines · 6.7 KB
--- title: Conflict detection description: Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items, and planned start and end date or the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/change-management/c\_ConflictDetection.html release: australia product: Change Management classification: change-management topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 3 breadcrumb: [Configure, Change Management, IT Service Management] --- # Conflict detection Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items, and planned start and end date or the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict. Conflict detection identifies conflicts for any of the following reasons: - The configuration items \(CIs\) are already scheduled at the given date and time. - A parent or child of the CI is already scheduled at the given date and time. - The CI is not in the maintenance window. - A parent or child of the CI is not in the maintenance window. - The CI is in a blackout window. - A parent or child of the CI is in a blackout window. - The CI is assigned to a person already scheduled at the given date and time. Using the **change.conflict.useprogressworker** system property, you can manage the conflict detection process in two ways. By default, this property is set to false. Conflict detection then runs through the Change Management Worker \[chg\_mgt\_worker\] table and the Change - Conflict Detection flow \(which runs as a System user\). If you set this property to true, conflict detection uses Progress Workers instead. You can also manually execute conflict detection. For more information, see [Detect conflicts manually and review conflict details](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_RunManualConflictDetection.md). ## Conflict detection process Conflict detection can run automatically when you provide values for the Configuration item, planned start and end date fields in the change form. It can also run when any of these field values are updated. It runs as well when these field values are available and the change request state is updated. When conflict detection identifies conflicts, it updates the conflict status and conflict last run fields. You can review conflicts in the Conflict section of the Change Request form. ## Conflict detection process using flows When the **change.conflict.useprogressworker** system property is set to false, conflict detection runs through the Change Management Worker \[chg\_mgt\_worker\] table and the Change - Conflict Detection flow. The flow runs as a System user. To view the associated flow, select **Show Flows** on the Change Request form. ## Conflict Calendar You can choose to display a conflict calendar to view identified scheduling conflicts. For more information, see [Conflict calendar](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/change-conflict-calendar.md) - **[Detect change conflicts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/configure-conflict-properties.md)** Detect change conflicts by setting Change Management conflict analysis properties. Use the resulting information to calculate conflicts for change requests and review and modify the change to eliminate conflicts. - **[Create blackout and maintenance schedules in Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_CreateBlkoutMaintSched.md)** Use the Blackout and Maintenance windows to schedule a change. Blackout windows specify times during which normal change activity should not be scheduled. Maintenance windows specify times during which change requests should be scheduled. For example, create a blackout schedule for code freezes at the end of the year. - **[Schedule types in conflict detection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/schedule-types-conflict-detection.md)** Conflict detection uses maintenance, blackout, and information schedules to evaluate when change requests can be implemented. Each schedule type supports a category and optional ownership fields. - **[Configure a change request to monitor outside maintenance schedule conflicts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/monitor-maintenance-schedule.md)** Configure a change request to detect conflicts outside the maintenance window. Conflict detection flags planned start and end dates that fall outside the maintenance schedule, so you can modify the change schedule accordingly. - **[Conflict calendar](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/change-conflict-calendar.md)** The conflict calendar graphically represents the potential scheduling conflicts for a change request. Conflicts are identified as active change requests, blackout schedules, and changes scheduled outside maintenance schedules. Use the **Scheduling Assistant** to resolve any schedule conflicts. - **[Enable automatic change conflict detection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_RunAutomatedConflictDetection.md)** Automate conflict detection to run at specific intervals or when a change request is updated to immediately review the conflicts when the schedule dates are updated. - **[Detect conflicts manually and review conflict details](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_RunManualConflictDetection.md)** Run conflict detection manually for a change request. Review the conflicts detected either automatically or manually and resolve them by changing the schedules. **Parent Topic:**[Configuring Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/configure-change-management.md)
| title | Conflict detection |
| description | Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items, and planned start and end date or the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/it-service-management/change-management/c\_ConflictDetection.html |
| release | australia |
| product | Change Management |
| classification | change-management |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 3 |
| breadcrumb | ConfigureChange ManagementIT Service Management |