> 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.md).

# Incidents

- [What is an incident?](https://docs.spike.sh/incidents/what-is-an-incident.md): An incident is any issue that needs to be investigated and resolved, often one that affects your customers.
- [Incident lifecycle](https://docs.spike.sh/incidents/incident-lifecycle.md): The incident lifecycle covers the stages an incident moves through, from the moment it's triggered to when it's resolved.
- [Incident statuses](https://docs.spike.sh/incidents/incident-statuses.md): A status would determine the state of the incident among acknowledged or resolved
- [How to change incident status?](https://docs.spike.sh/incidents/how-to-change-incident-status.md): You can change an incident's status from all alerting channels without having to come to Spike.
- [Acknowledge timeout](https://docs.spike.sh/incidents/acknowledge-timeout.md): Acknowledge timeout automatically moves an acknowledged incident back to triggered state if it isn't resolved within a set time.
- [Grouping incidents](https://docs.spike.sh/incidents/grouping-incidents.md): Spike automatically groups repeated incidents so you can see how often an issue recurs and when it first appeared.
- [Priority and Severity](https://docs.spike.sh/incidents/priority-and-severity.md): Priority indicates how urgently an incident needs to be resolved. Severity indicates the degree of damage to your systems.
- [Mute alerts](https://docs.spike.sh/incidents/mute-alerts.md): Mute alerts on an incident to stop notifications for a set period without resolving it.
- [Reassign incidents](https://docs.spike.sh/incidents/reassign-incidents.md): Reassign an incident to any team member directly from the dashboard, incident page, or service view.
- [Sharing incidents](https://docs.spike.sh/incidents/sharing-incidents.md): Share any incident as a public link with customers, stakeholders, or your team.
- [Why does message parsing fail?](https://docs.spike.sh/incidents/why-does-message-parsing-fail.md): Message parsing fails when Spike cannot convert an integration's JSON payload into a readable format.
- [Rate limiting on duplicate incidents](https://docs.spike.sh/incidents/rate-limiting-on-duplicate-incidents.md): Spike rate-limits duplicate incidents to reduce noise when the same incident triggers repeatedly in a short window.
- [Resolve by Timer](https://docs.spike.sh/incidents/resolve-timer.md): Resolve by Timer automatically resolves incidents after a set duration if they haven't been manually resolved.


---

# 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.md?ask=<question>
```

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.