Change freeze/Backout schedule is not working

[Aswin S]

Hi Team,

We have configured a Change Freeze / Blackout Schedule for the 2026 calendar. However, when creating a change request and scheduling it within the blackout period, no conflict is being detected or displayed.

Could you please advise if there are any additional configurations required or if there might be a mistake in our current setup?

Any guidance would be appreciated.

Regards,
Aswin

[Itallo Brandão · Accepted solution]

Hi Aswin,

This is a common issue often related to the scope of the Blackout Schedule or the specific Configuration Item (CI) on the Change Request.

Here are the troubleshooting steps to fix it:

1. Check the "Applies to" Logic Blackout Schedules are not global by default; they apply to specific CIs.

• Open your Blackout Schedule definition.

• Check the "Applies to" field (or the Filter condition).

• If it is set to a specific Class (e.g., cmdb_ci_server), ensure the CI selected in your Change Request belongs to that class.

• Test: If your Change Request has the "Configuration Item" field empty, conflict detection often skips the schedule check. Try populating a relevant CI.
  
  

2. Verify Schedule Entries Creating the Blackout Schedule header is not enough; you must have active child entries.

• Open the Blackout Schedule record.

• Scroll down to the Schedule Entries related list.

• Ensure you have an entry specifically for 2026 (e.g., Start: 2026-01-01, End: 2026-01-15) and that the Type is correct.
  
  

3. Run Conflict Detection Manually Conflict detection might not run automatically depending on your properties (change.conflict.mode).

• On the Change Request form, look for the "Check Conflicts" Related Link (or button).

• Click it and wait for the message at the top.

• If it says "There are no conflicts", double-check Step 1.
  
  

4. Check Maintenance Schedule Property Ensure that Conflict Detection is actually enabled for your instance.

• Go to Change > Administration > Conflict Properties.

• Ensure "Run conflict detection automatically..." is checked for the trigger you expect (Insert/Update).
  
  

Hope this helps you identify the gap!

[Aswin S]

Great answer sir!! @Itallo Brandão  applied the same, working as expected. 

Thanks..