Detect change conflicts manually You can run conflict detection manually for a change request. Before you begin Before you can run conflict detection for a change, the following fields must be completed for the change request: Configuration item, except in advanced mode. In advanced mode, the Affected CIs field is required instead. Planned start date Planned end date 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 might 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. In order to evaluate all the CIs, set the mode to Advanced. Role required: admin or change_manager Procedure Navigate to Change > Open. Open the change request that you want to check conflicts for. Click the Conflicts tab. Click Check Conflicts. Any conflicts appear in the Conflicts Detected list. What to do nextYou can review the detected conflicts and resolve them.