> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting detection

> Diagnose why an issue wasn't detected or why one incident became several issues.

Work these symptom-first. Each section states what you are seeing, why it happens, and what to check. If an issue opened but nobody was notified, see [Troubleshooting notifications](https://docs.sazabi.com/triage/troubleshooting.md).

## An expected issue was not detected

The agent opens issues from what it finds during an investigation, not from static thresholds, so undetected usually means it never looked, or the data wasn't there.

* **The data isn't arriving.** Open the [Intake page](https://docs.sazabi.com/send-data/intake.md) and confirm logs from the relevant source are landing. If volume is zero, the problem is ingestion, not detection. See [Troubleshooting ingestion](https://docs.sazabi.com/send-data/troubleshooting.md).
* **Nothing investigated that window.** Detection follows investigation. If no question covered the affected time and service, no issue opens.
* **The issue exists but is muted.** A muted issue keeps its status, and a new report with the same name is counted on it instead of opening a new issue. Check the inbox for a muted match and review its mute hit count. See [Muting and suppression](https://docs.sazabi.com/detect/issues.md#muting-and-suppression).

## Several issues for one incident

You expected one issue but got several.

* Sazabi matches a recurrence to an existing open issue by its **stable name**. Distinct symptoms of one root cause can legitimately produce distinct issues: a database outage may surface as separate anomalies in several services.
* Link the related issues to the same [component](https://docs.sazabi.com/triage/status.md) so the status page shows one degraded service rather than scattered issues.
* Resolve the duplicates you don't need; resolved issues leave the active inbox but stay searchable.

## Getting help

If an issue still isn't detected after these checks, gather the project, the affected time window, and the issue name (if one exists), then [contact support](https://docs.sazabi.com/manage/support.md): choose **Contact support** in the dashboard's command palette, or run `npx -y @sazabi/cli@latest support ask` from your terminal.

## Further reading

> [card] [Troubleshooting notifications](https://docs.sazabi.com/triage/troubleshooting.md)
>
> When an issue opened and nobody was notified.

> [card] [Troubleshooting ingestion](https://docs.sazabi.com/send-data/troubleshooting.md)
>
> When the data itself isn't arriving.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.