> ## 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 notifications

> Diagnose why a notification didn't arrive, why one reached the wrong channel, or why a channel is missing from your delivery rules.

Work these symptom-first. Each section states what you are seeing, why it happens, and what to check. If the issue itself was never opened, see [Troubleshooting detection](https://docs.sazabi.com/detect/troubleshooting.md) instead.

## I didn't get notified

An issue opened but nothing reached you.

* **Personal channel not on.** Personal delivery is gated by *your* preference. Open [**Settings > Notifications**](https://app.sazabi.com/settings/notifications) and confirm the channel is on for that event type. In-app and email are on by default. Slack DM and SMS are opt-in.
* **No matching delivery rule.** Shared delivery is positive: a shared channel receives an event only when a rule names both the event type and that destination. Check the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page for a rule covering the event.
* **A condition filtered it out.** If the rule has a severity, type, component, or owning-team condition, an issue that doesn't match won't reach the channel. A rule that selects only **high** skips **critical** issues, so select both. A rule that selects only a component skips issues linked to another one. Edit the rule's conditions under [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications).
* **The destination isn't connected.** A rule can only target a destination whose integration is connected. Connect it under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations), then add the rule again.
* **Issue events skip email by default.** Issue events such as triggered, resolved, ignored, updated and re-opened stay in the bell feed but do not send email unless you turned email on for them under [**Settings > Notifications**](https://app.sazabi.com/settings/notifications).

To see the rules a project has and the channels it can reach, run:

```bash theme={"system"}
npx -y @sazabi/cli@latest notifications delivery-rules list
npx -y @sazabi/cli@latest notifications channels get
```

See [Route notifications](https://docs.sazabi.com/triage/notifications.md) for the full routing model.

## A notification reached the wrong channel

A channel got events you meant to send somewhere else, or a team's channel is flooded.

* **Another rule matches.** Delivery rules only add delivery, so any enabled rule that matches the event sends it. List the rules and look for a broad one with no severity, type, or component condition.
* **The severity condition is too wide.** Select only the severities you want in that channel, such as **high** and **critical**. See [Issue lifecycle and severity](https://docs.sazabi.com/triage/lifecycle.md#use-severity-to-keep-a-project-quiet).
* **Security issues aren't separated.** Add a **Match by type** condition set to **security** on the rule for your security channel, and keep the other rules from matching those issues.

## Getting help

If a notification still doesn't arrive after these checks, gather the project, the issue name, the event type, and the delivery rule or personal preference you expected to match, 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] [Issue lifecycle and severity](https://docs.sazabi.com/triage/lifecycle.md)
>
> What each severity means and how issues change state.

> [card] [Troubleshooting detection](https://docs.sazabi.com/detect/troubleshooting.md)
>
> When an expected issue never opened.


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