Round Robin Scheduling is an incident assignment strategy where users are placed in a ring and assigned to incidents sequentially. This strategy can help ensure that incidents are equitably distributed, especially if they cluster during a single on-call shift. It can also lower incident response time if a service experiences concurrent incidents, since the incidents will not all be assigned to the same responder.
Round Robin Scheduling is available for accounts on our Business and Digital Operations plans. If you are interested in changing to a pricing plan that includes Round Robin Scheduling, please feel free to contact us for more information.
Follow the instructions to create an escalation policy, making sure to select the option to Assign via Round Robin in step 3.
- Navigate to People Escalation Policies click the to the right of your desired escalation policy and select Edit. In the level(s) where you would like to enable Round Robin, check the box Assign via Round Robin.
- Add users or schedules to the escalation level.
- When it’s a schedule’s turn for incident assignment, whoever is currently on call for the schedule will be assigned to the incident.
- Click Save.
When an incident triggers on any service that uses this escalation policy,
incidents will be assigned in sequential order to the users and/or schedules participating in the round robin rotation.
With Round Robin Scheduling enabled, you’ll see a green arrow next to the user who is next in line for incident assignment.
- Navigate to People Escalation Policies click the to the right of your desired escalation policy and select Edit.
- Uncheck the Assign via Round Robin checkbox underneath each escalation level where you would like Round Robin Scheduling disabled.
- Click Save.
Round Robin Scheduling uses an assignment ring to determine who to assign an incident to. The starting point of the ring is determined by the user order when the escalation policy is created. For example, if you enable Round Round Scheduling on an escalation policy and add User 1 followed by User 2, the starting point of the ring will be User 1.
When users or schedules are added to or removed from an escalation level with Round Robin Scheduling enabled, the following occurs:
- Any users or schedules removed from the escalation policy level are also removed from the assignment ring.
- Any users or schedules added to the escalation policy level are appended to the back of the ring in the order that they were added.
- The ring resets and points to the first user or schedule.
Example: let’s say we have a round robin rotation with three users, and User 2 is set to receive the next incident.
Next we add User 4 and User 5, and save. They are added at the back of the assignment ring and the assignment ring resets back to User 1.
When an escalation policy with Round Robin Scheduling is requested as part of a responder request, either manually or as part of an Incident Workflow, the request will go to the user who is at the front of the assignment ring and the ring will rotate.
An escalation policy with Round Robin Scheduling has three users and User 2 is at the front of the assignment ring. During the course of an incident on a different service, someone requests the escalation policy as a responder. User 2 will receive the responder request and User 3 will now be at the front of the assignment ring.
If a Round Robin Scheduling escalation policy is part of an Incident Workflow’s responder request along with other users, all users indicated in the Workflow will receive responder notifications, and the assignment ring will rotate.
When a schedule is due for assignment next, PagerDuty attempts to assign the incident to whoever is currently on call on that schedule. In cases where no one is on call, due to a coverage gap, for example, PagerDuty will skip the schedule and assign the incident to the next user or schedule in the assignment ring. This ensures that a coverage gap on a schedule does not cause an incident to be missed.
When this skip due to a coverage gap happens, the schedule will remain at the front of the assignment ring, and PagerDuty will attempt to assign the next incident to it.
If a responder does not acknowledge the incident within the escalation timeout period, the incident will escalate to the next level of the escalation policy — it will not rotate between users or schedules at the same escalation level. To learn more about escalation policies and escalation timeouts, please see Escalation Policy Basics.
If a responder does not acknowledge an incident within the escalation timeout period and the escalation policy is set to repeat, Round Robin Scheduling will attempt to assign the incident to the next user or schedule in the assignment ring.
When an incident is reassigned to the same escalation policy, this will also prompt Round Robin Scheduling to assign the incident to the next user or schedule in the assignment ring.
If your account uses the Live Call Routing feature, please note that it may attempt to contact all on-call responders on an escalation level in certain situations. This is Live Call Routing's default behavior when there are multiple users or schedules on an escalation level and Live Call Routing is configured to connect directly to the on-call user.
Updated about 15 hours ago