ServiceNow Blackout did not work for a change even after the CIs were added under Affected CIs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
56m ago
Hi Everyone,
Alerts were triggered for the Affected CIs listed in a change. It is assumed that once a CI is marked as an Affected CI on the Change Request, it will be put into Maintenance mode during the planned change start and end times, which should suppress alerts.
I'm yet to work on Event Management and I checked the Event Management module is being used, and this is the first time it happened like. Requesting guidance for debugging this issue.
Thank you!!
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
42m ago
Hi @Shidhi
Check this KB :
1. KB0711926 Blackout schedule does not appear on change request
Resolution
Set the system property “change.conflict.blackout” to true to ensure that platform will attach the blackout schedule or maintenance window after conflict detection run on change request
Resolution
Modify/update the affected blackout window schedule record “type” value to “blackout”.
— you can modify this value from the list view or add the type “field” on the blackout schedule form.
This should fix the issue when we run the conflict detection for a change request.
Also check:
