> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/incidents/incident-statuses.md). # Incident statuses Every incident on Spike moves through three statuses: triggered, acknowledged, and resolved. The current status determines whether Spike is actively alerting, paused while someone works on a fix, or closed. ## Triggered An incident enters the triggered state the moment it's triggered. This means no one has looked at it yet and the problem is unresolved. In this state, Spike works through the [escalation policy](/escalations/introduction-to-escalations.md) attached to the integration and sends alerts to the designated responders. Alerts continue until someone acknowledges or resolves the incident. Repeat incidents from the same integration are suppressed and logged rather than creating new ones. ## Acknowledged An acknowledged incident means someone is actively working on a fix. Spike pauses the escalation policy and stops escalating alerts. Repeat incidents remain suppressed in this state to reduce [alert fatigue](/alerts/personal-alerts-management.md). You can set an [acknowledge timeout](/incidents/acknowledge-timeout.md) for each integration. If the incident isn't resolved within that window, Spike moves it back to triggered and resumes alerting. ## Resolved A resolved incident means the issue is fixed. Spike stops all alerts and resets the escalation policy. If the same integration triggers a new incident after resolution, Spike treats it as a fresh incident and starts the process from the beginning. See [incident lifecycle](/incidents/incident-lifecycle.md) for the full flow. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.spike.sh/incidents/incident-statuses.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.