---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Change lockdown conflict detection

# Change lockdown conflict detection {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Conflict detection checks change requests against active lockdown records in the same run that checks maintenance windows and blackout windows. A change request that falls inside a lockdown period is reported as a conflict
and automatically placed on hold.

The property controls whether conflict detection checks against lockdown records. The property is shipped with the value `true`, so lockdown checking is active by default. For more information, see [Conflict detection properties](https://www.servicenow.com/docs/B2HpucwNAJGAFMvbGWRhAQ#conflict-detection-properties "Conflict detection includes properties that determine how the conflict detection capability is executed.").

## Conflict detection triggers {#lockdown-conflict-detection__section_conflict_triggers}

By default, conflict detection runs whenever one of the following values on a change request changes:

* The state of the change request
* The configuration item
* The planned start date or the planned end date

{#lockdown-conflict-detection__ul_conflict_triggers}

Any of these changes triggers a run. A new change request that falls inside a lockdown is placed on hold as soon as you submit it, regardless of the change request state.

You can narrow this behavior to a single state of a change model by using the Allow Conflict Detection model state attribute. When the attribute is present on one state, conflict detection runs only
when the change request reaches that state. For more information, see [Limit conflict detection to a change model state](https://www.servicenow.com/docs/ICGjn4l0pKUxpvH0BgWeIQ "Use the Allow Conflict Detection attribute to limit conflict detection to a specific change model state. Conflict detection then runs only when a change request reaches that state.").

## Lockdown conflict results {#lockdown-conflict-detection__section_conflict_result}

A change request that falls inside a lockdown period shows a conflict of type Inside Change Lockdown
Conflicts tab, with the lockdown record named in the Schedule column. The Conflict status field is set to Conflict, , and the
On hold reason field records which lockdown caused the hold.

Rescheduling the change request outside the lockdown period triggers a new conflict detection run. The lockdown conflict is removed, the on hold reason is cleared, and the change request can continue through its states.
* **[Limit conflict detection to a change model state](https://www.servicenow.com/docs/ICGjn4l0pKUxpvH0BgWeIQ)**   
  Use the Allow Conflict Detection attribute to limit conflict detection to a specific change model state. Conflict detection then runs only when a change request reaches that state.

**Related concepts**   

* [Change lockdown](https://www.servicenow.com/docs/_FlwAKV4BLQWcpGJZX079Q "Change lockdown allows change managers to pause all or a subset of in-flight change requests. Use it during major unplanned IT, critical, or financial events.")  
**Related tasks**   

* [Limit conflict detection to a change model state](https://www.servicenow.com/docs/ICGjn4l0pKUxpvH0BgWeIQ "Use the Allow Conflict Detection attribute to limit conflict detection to a specific change model state. Conflict detection then runs only when a change request reaches that state.")