> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/alarm/check-and-clear-alerts.md).

# Check and Clear Alerts

Review what fired in your Inbox, filter by severity or status, and resolve home alerts to stop escalation.

When an alarm fires, Chirp records it in your Inbox. This is where you see what happened, when it happened, and whether it still needs your attention. Resolving an alarm stops its [escalation chain](/alarm/escalation-chains.md) — no further steps fire once the event is marked as resolved.

Choosing **Alarm** in the sidebar takes you to the Inbox tab first.

## How do I filter alerts?

Two dropdown filters sit above the alarm list:

| Filter       | Options                                         |
| ------------ | ----------------------------------------------- |
| **Severity** | All severity, Critical, High, Medium, Low, Info |
| **Status**   | All status, Active, Resolved                    |

Use these to focus on what matters right now — for example, show only **Critical** + **Active** to see emergencies that still need attention.

## How do I search for an alert?

A search input lets you filter by alarm title. Start typing and the list narrows to matching results. If nothing matches, Chirp shows: *"We can't find your alarm."*

## What does the alarm list show?

On desktop, each alarm appears as a row with these columns:

| Column            | What it shows                                                                                                                        |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Alarm**         | The alarm title (or definition name), with a status indicator — a warning triangle for active alarms, a checkmark for resolved ones. |
| **Message**       | The notification message body.                                                                                                       |
| **Severity**      | The severity level, color-coded.                                                                                                     |
| **First trigger** | When the alarm first fired.                                                                                                          |
| **Last trigger**  | When the alarm most recently fired.                                                                                                  |
| **Actions**       | **Mark as resolved** button and a link to the originating rule.                                                                      |

On mobile, alarms appear as compact cards with the same information in a condensed layout.

### Empty state

If no alarms have fired yet, the Inbox shows: *"No alarms yet — To see alarms, create a rule and let it generate activity."*

## How do I resolve an alarm?

Click **Mark as resolved** on an active alarm to mark it as resolved. This does two things:

1. The alarm status changes from **Active** to **Resolved** — the indicator switches from a warning triangle to a checkmark.
2. Any remaining [escalation steps](/alarm/escalation-chains.md) for this event are canceled. No further notifications are sent.

Resolved alarms stay in the Inbox for your records. They do not disappear.

## How do I open the rule behind an alarm?

Each alarm has a link that navigates to the automation in the Rules Engine that triggered it (at `/rules/:ruleId/view`). This is useful when you need to understand why the alarm fired — what conditions were met, what sensor data triggered it, and whether the rule logic needs adjusting.

## What are good habits for handling alerts?

* **Resolve alarms when the issue is handled.** An unresolved alarm continues to escalate and re-send notifications. Resolving it is how you tell Chirp "I've seen this and it's under control."
* **Use severity filters during busy periods.** If you have many alarms, filter to Critical and High first to prioritize what needs immediate action.
* **Check the originating rule if an alarm seems wrong.** If an alarm fires unexpectedly, the Rules Engine rule might have a condition that is too sensitive or a sensor that is reporting unexpected data.
* **Resolve alerts from your phone.** If you have the [Chirp Alerts app](/alarm/chirp-alerts-app/managing-alerts.md) installed, you can resolve and manage alerts directly from your phone without opening the web platform.

## Why does an alert appear again?

Marking an incident resolved does not fix the underlying condition or turn off the rule. Later qualifying readings can raise it again. Check the sensor, [trigger timing](/rules-engine/triggers/trigger-timing.md), and suppression settings before changing your notification setup. Scroll within the inbox to review the rest of a long list.