On-Call Prep permissions and limits
This page lists who can use On-Call Prep, the rules Oppex follows when it chooses your shift and the incidents to show, and the messages you may see on the page.
Permissions
| Action | Who can do it |
|---|---|
| Open On-Call Prep | Every user, for their own shift only |
| Review an incident and give feedback on a key insight | Every user, on their own On-Call Prep page |
| See another person's On-Call Prep | Nobody |
Limits and rules
| Rule | Detail |
|---|---|
| Workspace | The page shows the workspace you are working in. Predictions must be switched on for that workspace, or the page shows Predictions are off. |
| Which shift | The shift you are on call for now. When you are not on call, the next shift that starts within 7 days. A workspace can use a window of 1 to 14 days instead. |
| Several schedules | The current shift wins over a later one. When two schedules give you exactly the same window, Oppex shows them as one shift and combines their services. Oppex considers up to 20 of your schedules. |
| Direct assignment | A shift on a schedule wins over being assigned directly to an escalation level. With only a direct assignment, the shift card reads You're always on call. |
| Services covered | The services whose escalation policies reach you during the shift. |
| How many incidents | Up to five in Regular alerts and up to five in Infrequent but likely this shift, for the whole shift. |
| Which incidents | Alerts that happened recently on those services and look likely during the shift. An infrequent alert is listed only when it looks likely during the shift, so that list is often empty. |
| History used | By default, the last 90 days of incidents on those services. Seen counts the times the incident happened in that period. |
| When the lists are calculated | Every night. A shift that is new or changed after the nightly calculation shows Not ready yet until the next night. |
| Key insights | Prepared after the nightly calculation. Until they are ready, the page shows "Insights are being prepared…". |
| Time zone | Times on the page use your own time zone preference. |
| Banner | Shown under the breadcrumb of the main list pages (Incidents, Services, Policies, Schedules, Teams, Users and Reports) while you are on call now or your next shift starts within 7 days and predictions are switched on. It does not appear on Settings pages, on a page for a single schedule or service, or on the On-Call Prep page itself. You cannot dismiss it. It does not depend on Notify On Call. |
| Reviewed | An incident is reviewed when you open it and it has key insights. The readiness percentage is reviewed incidents divided by incidents with key insights. |
Messages
| Message | Meaning | What to do |
|---|---|---|
| Predictions are off: "Likely-incident predictions aren't switched on for this workspace." | Predictions are not switched on for the workspace you are working in. | Nothing. The banner and the likely-incident list in reminder emails also do not appear. |
| No upcoming shift: "You're not on call now or in the next 7 days, so there's nothing to prepare for yet." | You have no current shift and none starting within the window. The number of days is 7 unless your workspace uses a different window. | Check your shifts in My Shifts. |
| Not ready yet: "Predictions for this shift aren't ready yet. They're calculated every night, so check back tomorrow." | Oppex has not yet calculated this shift, for example because it was added today. | Check back the next day. |
| Nothing likely for this shift: "No incident has happened often enough recently on your services to be likely during this shift." | No incident on your services recurred often enough to be listed. | Nothing. |
| Predictions unavailable: "Predictions aren't available right now. Please try again in a few minutes." | Oppex could not read the lists. | Click Try again. |
| Couldn't load On-Call Prep | The page could not be loaded. | Click Try again. |
| "Insights are being prepared…" | Oppex is still building the key insights for the shift. | Reload the page after a few minutes. |
| "No clear cause found in past notes and RCAs." | The notes on similar past incidents do not point to a cause. | Open the similar incidents to look yourself. |
| "No insights — this incident isn't grouped with similar ones." | The incident has no group, so Oppex has no similar incidents to read. | Nothing. |
| "Not enough past data to suggest causes yet." | Oppex has too little history on similar incidents to suggest causes. | Nothing. |
| "Insights couldn't be generated this time." | Oppex could not build the key insight. | Check again after the next nightly calculation. |
| "Couldn't load similar incidents." next to Retry | The similar incidents could not be loaded. | Click Retry. |
| "No similar past incidents were found." | Oppex found no similar past incidents. | Nothing. |