Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Detect conflicts manually and review conflict details

Log in to subscribe to topics and get notified when content changes.

Detect conflicts manually and review conflict details

You can run conflict detection manually for a change request and cancel conflict detection before it completes. You can review the conflicts detected either automatically or manually.

Before you begin

Before you can run conflict detection for a change request, the following fields must be completed.
  • Configuration item, except in advanced mode. In advanced mode, the Affected CIs field is required instead.
  • Planned start date
  • Planned end date

For more information about running conflict detection automatically, see Enable automatic change conflict detection

Prior to running conflict detection, you must consider the following scenarios unique to your organization.
CMDB list size and relationship complexities
If you are 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 switched off by default
When you upgrade, advanced mode conflict checking is switched off by default. Hence, affected CIs are not considered during conflict detection. To evaluate all the CIs, set the mode to Advanced.

Role required: itil


  1. Navigate to Change > Open.
  2. Open the change request to check conflicts.
  3. Click the Conflicts tab or scroll to the form section.
  4. Click Check Conflicts.
    The Checking conflicts progress status pop-up window appears. To cancel without detecting conflicts, click Cancel.
  5. When conflict detection is finished, click Close in the pop-up window.
    Conflicts appear in the Conflicts Detected list. The Conflict status and Conflict last run fields in the form are updated.
  6. Review the list of conflicts that appear, and click the more information icon to view the details of a conflict.
    Table 1. Conflict form fields
    Field Description
    Change A reference to the scheduled change that has a conflict.
    Conflicting change The change that is in conflict with the scheduled change, if any.
    Affected CI The affected CI associated with the change.
    Last Checked The last time the conflicts were checked. The Last Checked field is automatically updated.
    Related CI The parent CI or child CI of the current CI, if it has caused a conflict.
    Schedule The name of the maintenance window or blackout window that is causing the conflict, if any.
    The issue that caused the conflict.
    • 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