> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://fyno.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://fyno.io/docs/_mcp/server.

# Alarms

> Monitor, investigate, and resolve notification delivery issues with Alarms. Track severity, occurrences, anomalies, and recommended fixes in Fyno.

**Alarms** give you a single place to see every issue Fyno detects while delivering notifications to your users, from provider errors and rate limits to template changes made by channels like Meta. Each alarm is tagged with a severity so you can decide what to fix first. Addressing alarms promptly keeps your deliverability healthy and makes sure your notifications consistently reach your users.

> **Note**
>
> The full Alarms page is available only on paid plans. On the free plan, you can see the Alarms summary on the Dashboard.

## Alarms summary on the Dashboard

The **Alarms** card on your Dashboard shows how many alarms are currently unresolved, broken down by severity. Click **View All** to open the Alarms page.

![](/docs/_fern-img/cfcd8af81d1941bda8c397b8d65ce5d2831820b5573cd4d2cf57da23fa0ee2a0.webp)

### Severity levels

| Severity   | What it means                                                                                            |
| ---------- | -------------------------------------------------------------------------------------------------------- |
| **High**   | Issues that stop or seriously affect delivery, such as a template rejected by Meta. Address these first. |
| **Medium** | Issues that affect delivery for part of your traffic and should be looked at soon.                       |
| **Low**    | Recurring errors that affect individual requests, such as rate limiting or missing data.                 |
| **Info**   | Informational events worth knowing about that don't need immediate action.                               |

## Alarms page

The Alarms page lists every alarm raised in your workspace.

![](/docs/_fern-img/8c40d6a7e7a74cf827dcc54b20bc6efbeaa336808e881a8fd4006f38d16a346e.webp)

### Status tabs

Alarms are split into three tabs, each showing the number of alarms it contains.

| Tab           | Contains                                                |
| ------------- | ------------------------------------------------------- |
| **Open**      | Alarms that are active and haven't been resolved yet.   |
| **Re-opened** | Alarms that were marked as resolved but occurred again. |
| **Resolved**  | Alarms that have been marked as resolved.               |

### Filters

Use the filters at the top right to narrow down the list.

* **Module**: shows only the alarms raised in a specific part of Fyno, such as a notification event, workflow, webhook, provider, integration, or WhatsApp template.
* **Severity**: shows only alarms of the selected severity.

### How alarms are grouped

Alarms with the same description are grouped into a single row. The number in brackets next to the description is the number of alarms in that group. For example, **Meta category change from Utility to Marketing (2)** means two templates have raised this alarm. Click the arrow next to a row to expand the group and see each individual alarm.

### Columns

| Column                   | Description                                                                                                          |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| **Description / Module** | Why the alarm was raised, for example `ratelimited` or `INVALID_PROVIDER: The provider is not available/configured`. |
| **Started**              | When the alarm was first raised, for example *29d ago*.                                                              |
| **Last Occurrence**      | When the alarm was last seen, for example *5h ago*.                                                                  |
| **Occurrences**          | How many times the alarm has occurred in total.                                                                      |
| **Severity**             | The severity of the alarms in the group, with a count for each, for example *High: 2*.                               |

You can sort by **Started**, **Last Occurrence**, and **Occurrences** by clicking the column header.

> **Tip**
>
> Some alarms are raised by a one-time change rather than by repeated delivery failures, for example when Meta rejects a template or changes its category. These alarms show `0` occurrences and `-` as the last occurrence, but they stay open until you resolve them.

## Alarm details

Click any alarm to open its details.

![](/docs/_fern-img/7ded9edcd66c555ba6006c853a733cb6bbb6f426a0123ff456a97077921dc184.webp)

The details view contains:

* **Title and status**: the alarm description and its current status (Open, Re-opened, or Resolved), along with who opened it and when.
* **Explanation**: a short description of what happened. Click **Learn More** to read more about the issue.
* **Module and Source**: the module where the alarm was raised and the specific resource that caused it, such as the template name. Click the link icon next to the source to open it directly.
* **Integration(s)**: the integration involved, along with its account identifier. For WhatsApp, this is the **WABA / Namespace**.
* **Recommended Solution**: suggested steps to fix the issue, where available.

### Resolving an alarm

Once you've fixed the underlying issue, click **Mark as Resolved**. The alarm moves to the **Resolved** tab. If the same issue occurs again, the alarm moves to the **Re-opened** tab so you know the fix didn't hold.

### Viewing the change log

To see the history of an alarm, click the **history** icon at the top right of the alarm details. The **Alarm History** panel lists every status change with its date and time, who made it, and any note added. Alarms that re-open automatically are shown as re-opened by **Fyno AI**. This is useful when an alarm has been re-opened and you want to know who resolved it earlier.

![](/docs/_fern-img/f327bf2ecfee8e728f5520a0df5a191aa655936d8ed9d0c73f4d2207cb92bfa5.webp)

## Anomalies

Fyno also watches your delivery trends for unusual spikes or drops, called **anomalies**. Click **Past Anomalies** at the top right of the Alarms page to review anomalies detected in your workspace.

![](/docs/_fern-img/8c227d8c9df0df81aab899af1793d023641ae706e24193a100af4294ddaf8ac7.webp)

The anomaly chart plots delivery status over time so you can see exactly when and how the pattern changed:

* **Channel**: use the dropdown in the chart title to switch between channels, for example **Email Delivery Status**.
* **Status lines**: **Requested**, **Delivered**, **Bounce**, and **Error** are plotted separately. Click a status in the legend to show or hide it.
* **Count or percentage**: use the **#** and **%** toggle at the top right to switch between absolute numbers and percentages.
* **Zoom**: use the zoom controls at the bottom right to focus on a specific time range.