# Incidents - [What is an incident?](https://docs.spike.sh/incidents/what-is-an-incident.md): Learn the basics of an incident. - [Incident lifecycle](https://docs.spike.sh/incidents/incident-lifecycle.md): Lifecycle of an incident. - [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): Responders can choose to change incident status on phone alerts, Slack and on the dashboard. - [Acknowledge timeout](https://docs.spike.sh/incidents/acknowledge-timeout.md): Set a timeout for when an incident is acknowledged but not resolved in the given time frame. Acknowledge timeout helps your team by reminding you of incidents in non-resolved state - [Grouping incidents](https://docs.spike.sh/incidents/grouping-incidents.md): Repeated incidents will be grouped together. - [Priority and Severity](https://docs.spike.sh/incidents/priority-and-severity.md): Determine and set incident's priority to indicate urgency and severity to indicate possible damage - [Mute alerts](https://docs.spike.sh/incidents/mute-alerts.md): Mute all alerts 🚨 (or switch off all alarms) for an incident so you can continue your work fixing it. - [Reassign incidents](https://docs.spike.sh/incidents/reassign-incidents.md): Reassign the incident to any of your team mates - [Sharing incidents](https://docs.spike.sh/incidents/sharing-incidents.md): Share your incidents with the world, embed in your docs and more. - [Why does message parsing fail?](https://docs.spike.sh/incidents/why-does-message-parsing-fail.md): We parse the data integrations send in JSON to human readable format. Sometimes it fails. What does it mean and why does it happen? - [Rate limiting on duplicate incidents](https://docs.spike.sh/incidents/rate-limiting-on-duplicate-incidents.md): Rate limiting for duplicate incidents. - [Resolved by Timer](https://docs.spike.sh/incidents/resolve-timer.md): Resolved by Timer resolves incidents after a specified time period. --- # Agent Instructions: 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= ``` 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.