You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are implementing a feature to set a 'backup' caller who will be available for call in our software, this is generated when someone starts through the previous member of the same rotation. In cases where the next person to be on call has been over-ridden, we want to select the person who has been over-ridden to be the backup caller.
The 'Who is On Call' currently correctly shows 'exactNextOnCallParticipants' for multiple rotations, however where we could expect 'nextOnCallParticipants' to show next on call for both rotations before overrides, this isn't the case. We only get 1 entry.
The image describes our current example case. As CH comes online, HS will want to be on backup.
Querying the 'Who is On Call API' for the next person to be on call is expected to respond with:
however we get:
We are unsure why HS is being omitted here other than because they are on a separate rotation, however CH is shown what ways do we have to access who was overridden if not for this endpoint?
Hi @Lee Herring !
That is the intended behavior for the on-call API - it lines up with how Opsgenie escalates issues within a single on-call schedule as well:
Generally, rotations are meant to separate things like regional teams. If you are looking to set up a backup then the best option is to break that out into its own "backup schedule" instead of a backup rotation. That would give you a little more control over when to notify users in each of those rotations.
That will also let you pull who is on call and who is backup using the on-call endpoint here (albeit with two requests): https://docs.opsgenie.com/docs/who-is-on-call-api#get-on-calls
Please let me know if you're still running into issues getting this up and running, but it sounds like that might resolve most of the problems you're running into!