When an incident is over, Vibe AI helps you close it out cleanly — confirming the resolution, notifying the war room, generating a postmortem, and (optionally) tidying up the channels that were spun up to coordinate the response. This page covers how to resolve an incident and what happens when you do. For the full incident state model and severity levels, see Incident Lifecycle.
There are three ways an incident reaches the Resolved state.
Vibe AI continuously monitors the conversation and context tied to an incident. When it detects language signaling the issue is fixed (e.g. "DB is back to healthy", "customers confirmed it's working again"), it can update the incident to Resolved automatically.
<aside> ℹ️
If the incident's current state was set manually by a responder — or pushed in from an external provider such as PagerDuty — Vibe AI will not silently overwrite it. Instead, a green Resolution Detected badge appears on the incident header and dashboard card as a hint. Review the context and confirm if you agree. See Incident Lifecycle for details.
</aside>
In chat, Vibe AI may also post a "This incident appears to be resolved" prompt in the war room with quick buttons to confirm (Yes, mark as resolved) or dismiss (No, keep investigating).
Tag @Vibe AI in any monitored channel (Slack or Teams) and say it in natural language — there are no fixed commands:
@Vibe AI incident #1234 is resolved, the fix is deployed@Vibe AI #1477 is good now, customers confirmedVibe AI applies the change and confirms it in the thread.
Click the status badge on the Incidents Dashboard or Incident Detail page and select Resolved. On the Enhanced Dashboard you can also drag an incident card into the Resolved column. The change takes effect immediately.
When an incident is marked resolved, Vibe AI runs a few wrap-up steps automatically:
| Step | What happens |
|---|---|
| Resolution message | Vibe AI posts an “Incident Resolved” message in the war room with a link to the incident’s postmortem and portal page. |
| Postmortem & RCA | A postmortem can be generated for the incident, capturing the timeline, root cause, and follow-ups. |
| War room auto-archive | If enabled for your organization, the incident’s war room channel(s) are archived automatically (see below). |
| Timeline record | Each wrap-up action is recorded on the incident timeline for an auditable history. |
For postmortem details, see Postmortem & RCA Generation.