> For the complete documentation index, see [llms.txt](https://oiadocs.cloudfabrix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oiadocs.cloudfabrix.io/features-guide/incidents/incident-states.md).

# Incident States

There are various states an incident resides after an incident is created. The state defines the current state of the incident. 

{% hint style="info" %}
The following incident states are as defined by CloudFabrix. However, ITSM tools may use similar names/terminology for different purposes. 
{% endhint %}

1. Starred - It is to store incidents like favorites so that a user can easily access incidents (more frequently used incidents).
2. To do - It is the first state of an incident that it will be in when an incident is created
3. Analyzing - It is the state where an incident is ingesting data from data-sources.
4. Review - Once the data analysis completed, the incident automatically moves to a Review state so that users can start working on the incident.
5. Failed - In case if the system comes across any issue during the analysis phase, the incident will be in the Failed state. The user needs to check and take corrective action on this incident or on the data analysis.
6. Archived - All the archived incidents reside here before they are purged and deleted by the defined purge configuration.
7. Throttled - During the creation of an incident, when there are more incidents created than defined in a particular time or if a job is taking more time to pull the relevant data while creating the incident, these incidents are moved into the Throttled state.  The user needs to check and rerun the jobs so that the incident will move into To do -> Analyzing -> Review.


---

# 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, and the optional `goal` query parameter:

```
GET https://oiadocs.cloudfabrix.io/features-guide/incidents/incident-states.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.