Every alert has a status that reflects its current state in the investigation and resolution workflow. Keeping statuses up to date helps your team prioritize urgent issues and avoid duplicate work.Documentation Index
Fetch the complete documentation index at: https://docs.datachecks.io/llms.txt
Use this file to discover all available pages before exploring further.
Statuses
| Status | Description |
|---|---|
| No Status | The initial state when an alert is first created. No action has been taken yet. |
| Investigating | A team member is actively examining whether the alert represents a genuine issue. |
| Fixed | The underlying problem has been resolved. No further action is needed. |
| Expected | The anomaly is statistically valid but was caused by an anticipated event — such as a pipeline change, scheduled maintenance, or a known data event. |
| No Action Needed | The anomaly is statistically valid but not significant enough to warrant investigation or remediation. |
| False Positive | The alert does not reflect an actual statistical anomaly or genuine problem and can be dismissed. |