> For the complete documentation index, see [llms.txt](https://docs.upriverdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upriverdata.com/product-usage/incidents/incident-status.md).

# Incident Status

The status of an incident can be changed by the user and serves the following purposes:

* **Improve communication** - Make sure all relevant stakeholder to know which incidents have been acknowledged, reviewed or dismissed. This allows you to ensure that no incident goes unhandled by your team.
* **Improve operational efficiency** - Track the number of incidents and the time taken to triage and resolve issues. This will help you see progress over time, set goals and communicate the effects of data quality to the rest of the organization.
* **Upriver's Model precision** - Upriver’s AI system takes in to consideration the status given to each incident by removing or setting weights according to the status in order to help set more accurate thresholds for each metric.

| Status          | Meaning                                                                               | Effect on Upriver's Model                                                                      |
| --------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Unresolved      | The incident was created and not yet triaged by a user.                               | No effect.                                                                                     |
| Under Review    | Someone is aware of this and is currently assessing whether it’s a significant issue. | No effect.                                                                                     |
| Fixed           | The issue was fixed and should behave like it did before.                             | Incident is ignored when retraining the model and the profile before the incident is expected. |
| Expected Change | The incident is valid but is the result of an expected change.                        | Retrain the model taking into consideration the new values.                                    |
| Misdetection    | The detection is not valid.                                                           | Retrain the model with taking into consideration the incident as a valid value.                |