Snooze an incident
Tool: oppex.incident.snooze
Snoozes one incident that is assigned to you for a number of minutes. While it is snoozed, Oppex stops reminding and escalating. When the snooze ends, Oppex starts paging again.
What you provide
| Input | Required | Description |
|---|---|---|
| Incident ID | Yes | The incident to snooze. |
| Duration in minutes | Yes | A whole number of minutes, at least 1 and no more than your workspace's maximum snooze. The maximum is 1440 minutes (24 hours) unless an administrator has changed it. |
Example prompts
- "Snooze the Millennium Falcon Worker incident for 45 minutes while I restart the hyperdrive."
- "Snooze my Sev-3 disk usage incident for two hours."
- "Snooze incident cacgichh-efbg-jv3t1ufo until the deploy finishes, about 30 minutes."
When you give the duration in hours, the assistant converts it to minutes.
Who can use it
Only the person the incident is currently assigned to can snooze it, whatever their role.
Limits and errors
| Message | Meaning |
|---|---|
| "Snooze duration must be at least 1 minute" | No duration, or a duration of 0, was sent. |
| "Snooze duration cannot exceed <maximum> minutes" | The duration is longer than your workspace allows. Ask for a shorter snooze. |
| "User can only snooze incidents currently assigned to them" | The incident is assigned to someone else. |
| Incident not found | No incident in your connection's workspace has that ID. |
| Incident already resolved | A resolved incident cannot be snoozed. |
What happens next
The timeline records who snoozed the incident and for how long. Snoozing does not send the service's email or Slack notifications. When the snooze ends, Oppex pages the on-call person for the incident's current level again.