Nobody Is On-Call


It is possible to have a schedule with gaps where no one is on-call during certain times. If no one is on-call at a certain escalation level, the incident will immediately escalate to the next level of the escalation policy. If no one is on-call on the entire escalation policy, an incident will not be created.

If you try to create a new incident in the web UI on a service where no one is on-call, you will get an error message that the Incident cannot be created. Any trigger events sent to an integration where no one is on-call will not trigger an incident.


If you want an incident to be created, but you do not want anyone to be notified or you do not want noisy notifications for an incident, this can be accomplished by setting up support hours on your service using low-urgency Notification Rules.

Have more questions? Submit a request


  • Avatar
    James West

    Would it be possible for the incident to be 'queued' so when the next persons on call schedule comes active it is assigned to them then?

  • Avatar
    Alexis Chu

    Hi James,

    Currently the best way to accomplish this is to create a "Nobody" user who can be assigned the incident when nobody is on-call. The next user on-call can review the incidents assigned to "Nobody" and ack them to assign the incidents to themselves.

    Alternatively, you can use our API to write a script that will automatically assign all "Nobody" incidents to the next on-call user:

    Email us at if you have any questions about the above.