Deactivating Notifications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
I am deactivating some custom notifications which are not required.I would like to know how to analyse the impact of deactivating them .How to validate the effect with Business rules or any other .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
When deactivating custom notifications, it’s a good practice to first analyze both technical and functional impact. Below are some effective ways to validate the impact before and after deactivation:
Identify the Triggering Mechanism
Check whether the notification is triggered by a Business Rule, Flow Designer, Event, or Script Include.
Review the When to send conditions and the associated event name (if any).
Search for Dependencies
Use Global Search / Script Search to find references of the event name in:
Business Rules
Script Includes
Workflows / Flow Designer
Custom scripts
This helps ensure the notification is not reused elsewhere.
Review Business Rules
Check Business Rules on the target table for:
gs.eventQueue() usage
gs.eventQueueUnique() usage
If the event is only used for this notification, deactivating it is usually safe.
Check Email Logs
Review sys_email and sys_email_log to understand:
Frequency of emails
Who is receiving them
Whether they are still relevant
Test in Sub-Prod
Deactivate the notification in DEV / TEST
Perform the same actions that previously triggered the notification
Validate that:
No required emails are missing
No errors appear in system logs
Monitor System Logs
After deactivation, monitor:
System Logs → Errors
Event Queue
This ensures no scripts or processes are failing silently.
Functional Validation
Confirm with stakeholders that the notification is no longer required
Ensure there is no compliance, audit, or SLA dependency
Following this approach helps ensure a safe and controlled deactivation without impacting business processes.
Hope this helps!
If this answers your question or provides clarity, please consider marking it as Helpful or Accept as Solution so it can help others in the community as well!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
My thoughts
- If the notifications are event‑based, identify the business rule or flow that triggers those events.
- Keeping the triggering logic active without disabling it will continue generating event log records. Even though emails won’t be sent, the event log table will keep growing unnecessarily.
- If the notifications are not tied to any events, you can safely deactivate them with no further impact
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Thank you for marking my response as helpful.
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
