---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Detect conflicts manually and review conflict details

# Detect conflicts manually and review conflict details {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Run conflict detection manually for a change request. Review the conflicts detected either automatically or manually and resolve them by changing the schedules.

## Before you begin

Before you can run conflict detection for a change request, the following information must be provided in the change record:

* The configuration item in either the Configuration item field or in advanced mode the Affected CIs field.
* The planned start date, provided in the Planned start date field.
* The planned end date, in the Planned end date field.

{#t_RunManualConflictDetection__ul_qhh_kkd_3t}  
Note:  
The conflict detection feature is unavailable if the Exclude from conflict detection check box in the Change Request form is selected. For more information, see [.](https://servicenow-prod.fluidtopics.net/uWeywcJWCXG8NmbgNukTaw#exclude-from-conflict-detection "Exclude change records from being displayed as a potential conflict in the conflict detection process.")

For information about running conflict detection automatically, see [Enable automatic change conflict detection](https://servicenow-prod.fluidtopics.net/WhxTMacVOFwKSVhGIs9how "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.").  
Prior to running conflict detection, consider the following scenarios:

CMDB list size and relationship complexities
:   If you have a large organization with a large CMDB, conflict detection can take longer to complete.

Inactive changes are not evaluated
:   Conflict detection does not evaluate inactive changes when determining conflicting changes.

Advanced mode conflict checking is disabled by default
:   When you upgrade the application, advanced mode conflict checking is disabled by default and affected CIs are not considered during conflict detection. To evaluate all CIs, set the mode to
    Advanced.

Role required: itil or sn_change_write

## Procedure

1. Navigate to AllChangeOpen.
2. Select the change request.
3. Select the Conflicts tab.
4. Select Check Conflicts.
5. When the conflict detection pop-up window is displayed, click Close.  
   Conflicts appear in the Conflicts Detected list on the Conflicts tab. The Conflict status and Conflict last run fields on the change request record are also updated.
6. In the Conflicts Detected list, review the list of conflicts.  
   {#t_RunManualConflictDetection__table_inx_bpg_ys__entry__2}

   | Field | Description |
   |-|-|
   | Conflicting change | Change that is in conflict with the scheduled change, if any. |
   | Affected CI | Affected CI associated with the change. |
   | Last Checked | The last time the conflicts were checked. The Last Checked field is automatically updated. |
   | Related CI | Parent CI or child CI of a current CIthat has caused a conflict. |
   | Schedule | Maintenance window or blackout window causing the conflict, if any. |
   | Type | Issue that caused the conflict. The available types are: * CI Already Scheduled * Parent CI Already Scheduled * Child CI Already Scheduled * Not in Maintenance Window * Parent Not In Maintenance Window * Child Not In Maintenance Window * Blackout {#t_RunManualConflictDetection__ul_w4x_bpg_ys} |
   [Table 1. Conflicts Detected List columns]

   {#t_RunManualConflictDetection__table_inx_bpg_ys}

## What to do next

Resolve any conflicts and reschedule the change.
**Related concepts**   

* [Conflict calendar](https://servicenow-prod.fluidtopics.net/I7dfJU_iBpGgC_duVHTFBg "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.")
* [Conflict detection](https://servicenow-prod.fluidtopics.net/_WGrzFTQyCw~c9cgC4OlEQ "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.")  
**Related tasks**   

* [Detect change conflicts](https://servicenow-prod.fluidtopics.net/HQtY4pGQb30K3L5cH7hUYg#configure-conflict-properties "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://servicenow-prod.fluidtopics.net/Gyeat1enp08Zj9DzXEzZrA "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. blackout-maintenance-schedule")
* [Configure a change request to monitor outside maintenance schedule conflicts](https://servicenow-prod.fluidtopics.net/4qha2Y2yPoZUitLS4JxHtg "When a change request is configured to display the conflicts that are outside the maintenance schedule, conflict detection indicates whether the planned start and end dates occur outside the maintenance window or not. By reviewing the conflicts that are detected, you can modify the change schedule.")
* [Enable automatic change conflict detection](https://servicenow-prod.fluidtopics.net/WhxTMacVOFwKSVhGIs9how "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.")

## Cancel conflict detection manually {#ariaid-title2}

Cancel any conflict detection jobs that are actively running for a change request if
you want to make any modifications to the schedules. After modifying the schedules, you can
rerun the check conflicts action again to identify potential conflicts.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllChangeOpen.
2. Open the change request that you want to cancel conflict checking for.
3. Click the Conflicts tab.
4. Click Check Conflicts.  
   The Checking conflicts progress status pop-up window appears.
5. To cancel conflict detection, click Cancel.  
   The active conflict detection job is canceled and all conflicts displayed in the Conflicts section are cleared. The Conflict Status field displays a Not Run status.  
   Note:  
   If you set conflict detection to run automatically or on a scheduled basis, the future executions of conflict detection against the same change request record are not canceled.

## Exclude change requests from conflict detection {#ariaid-title3}

Exclude change records from being displayed as a potential conflict in the conflict detection process.

### Before you begin

Role required: change_manager

### Procedure

1. Navigate to AllChangeOpen.
2. Select an existing change request.
3. In the form context menu, select ConfigureForm layout.
4. Add the Exclude from conflict detection field to the change request form.  
   For information on the procedure to add a new field to a form, see [Configuring the form layout](https://www.servicenow.com/docs/access?context=configure-form-layout&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

### Result

The Exclude from conflict detection check box is added to the Change Request form. When the check box is selected in the change request form, the Check conflicts option is
inactive, and the change request is excluded from the conflict detection process. The change request is also excluded from being displayed as a conflict when conflict detection is run on other change records.

*[\>]: and then