Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Understanding the purpose of the "On-Call Schedule - Gaps and Conflicts" notification

RaasheedRaS
Tera Contributor

Hi Community,

I'm trying to better understand the intent and business value of the "On-Call Schedule - Gaps and Conflicts" notification in ServiceNow On-Call Scheduling.

From my investigation, I found that:

  • The notification is triggered by the scheduled job "On-Call Gaps Conflicts Report".
  • The job reviews upcoming On-Call schedules and generates the event rota.on_call.report.
  • The script appears to evaluate future schedules for:
    • Coverage gaps (inactive users, users who left, time off without coverage, etc.)
    • Scheduling conflicts
  • Emails are sent only when gaps or conflicts are identified.
  • Recipients are dynamically selected (On-Call Admins, Rota Admins, Group Managers, Shift Managers, Delegated Managers).

My questions are:

  1. What is the primary business purpose of this notification?
  2. What actions are recipients expected to take when they receive it?
  3. How critical is this notification for On-Call operations?
  4. What are the operational risks of disabling or deactivating it?
  5. Has anyone deactivated this notification in production, and if so, what was the impact?
  6. Is it considered a core governance/health-check mechanism for maintaining On-Call schedules?

We recently observed the notification working as designed, but we are trying to determine whether it is merely informational or if it plays a critical role in preventing On-Call coverage and escalation issues.

Any insights from teams actively using ServiceNow On-Call Scheduling would be greatly appreciated.

Thanks!

0 REPLIES 0