Every incident in Vibe OnCall moves through a set of states that reflect its current status. Understanding these states helps teams maintain a shared, accurate picture of what is actively being worked on, what is resolved, and what has been cleaned up.

Incident States

State What it means
Open The incident has been declared and no one has started working on it yet.
Acked The incident has been noticed and a responder has taken ownership and started investigating.
Blocked The incident cannot move forward because the resolution depends on a third party and there is nothing the team can do until they respond.
Observation The incident appears to be fixed and the responder is monitoring the system to confirm it has stabilized.
Resolved The incident has been fully addressed and the system is confirmed stable. No further action is required.

There is no enforced transition order — incidents can be moved to any state at any time. This gives teams flexibility to reflect the real-world status of an incident rather than being constrained by a rigid workflow.

*Archived - The incident has been removed from the active incidents view. Archived incidents remain in the system for historical reference but are hidden

Incident Severity

Each incident carries a severity level that indicates its impact and urgency. Severity is displayed as a badge on both the incidents dashboard and the incident detail page, and can be updated at any time. Vibe AI auto-assigns the severity level per the corresponding conversational context.

Vibe AI supports the following severity levels, from highest to lowest impact:

Severity Label
Highest SEV0
↓ SEV1
↓ SEV2
↓ SEV3
↓ SEV4
↓ SEV5
↓ SEV6
Lowest Signal

Changing Incident State

Incident state can be updated in three ways:

1. Automatic detection by Vibe AI

Vibe AI continuously monitors the conversations and context associated with an incident. When it detects language that signals a clear change in status — such as a responder declaring the issue resolved — it will automatically update the incident state without requiring any explicit instruction or confirmation.

Examples of signals that trigger an automatic state update: