# Incident statuses

## What are different Incident statuses?

There are mainly 3 states -

1. **Triggered 🔥**
2. **Acknowledged** 👩‍💻
3. **Resolved** ✅

### **1. Triggered 🔥**

Every incident which comes to Spike will be first in the **triggered** state. It would mean that someone will need to look into this and address the problem.

Alerts are sent to members as long as an incident remains in this state.

### 2. Acknowledged 👩‍💻

An **acknowledged** state of the incident would mean that you have begun to look into the incident. Alternatively, this also means that work to resolve this incident has begun.

In this state, repeat incidents are automatically suppressed and logged reducing alert fatigue.

{% hint style="info" %}
We highly recommend setting an acknowledge timeout for all your incidents.
{% endhint %}

{% content-ref url="/pages/-LrrvGKNaILXZpnv5Fok" %}
[Acknowledge timeout](/incidents/acknowledge-timeout.md)
{% endcontent-ref %}

### 3. Resolved ✅

Once an incident is fixed, you mark it as **resolved**. This is the end state for all incidents.

If a similar incident is triggered then a new incident is created.


---

# 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/incident-statuses.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.