Acknowledge an incident
Tool: oppex.incident.acknowledge
Acknowledges one incident, exactly as the Acknowledge button in Oppex does. The incident moves to Acknowledged, the pending reminders and escalation stop, and the timeline records "Acknowledged by <your name>."
What you provide
| Input | Required | Description |
|---|---|---|
| Incident ID | Yes | The incident to acknowledge. The assistant finds it with List my incidents, List all incidents or Search incidents when you describe the incident by title. |
Example prompts
- "Acknowledge the Hyperdrive Failure incident on Millennium Falcon Worker."
- "Acknowledge incident cacgichh-efbg-jv3t1ufo."
- "I'm looking at the checkout latency alert now — acknowledge it for me."
- "Show my triggered incidents, then acknowledge the Sev-1 one."
Who can use it
You can acknowledge an incident if it is assigned to you, or if you are part of the escalation policy that handles the incident's current severity. Your role does not change this rule, so an administrator who is not on that policy cannot acknowledge the incident.
Limits and errors
| Message | Meaning |
|---|---|
| "You can only acknowledge incidents of an escalation policy you belong to" | The incident is not assigned to you, and you are not on the policy for its current severity. |
| Incident not found | No incident in your connection's workspace has that ID. |
| Incident already resolved | A resolved incident cannot be acknowledged. |
What happens next
- The incident's status changes to Acknowledged, and Oppex stops the escalation.
- The service's email and Slack notifications for the Acknowledged event are sent, naming you as the person who acknowledged it.
- An incident that is already acknowledged stays as it is.
If your workspace re-escalates acknowledged incidents after a timeout, that timeout still applies.