Manage alerts

Use the alerts list to see which alerts are healthy and which have failed. Open an alert to run it now, pause it, change it, delete it or check who receives its email. To create an alert, see Create an alert.

Find an alert and read its status

1. Open Observability > Alerts.
2. Read the list. Each row shows Name, Status, Schedule, Next Run, Last Run, Owner, Runs As, Last Error and Created At.
3. Use the search box to filter the list.

The list shows 50 alerts per page, and you can choose 100 or 200. It refreshes itself every 30 seconds. You can sort by Name, Status, Next Run, Last Run, Last Error and Created At. Schedule, Owner and Runs As cannot be sorted. New alert appears only when you can create alerts. If a refresh fails after the list has loaded, a slim error bar appears with the title Failed to load alerts and a Retry button, and the list stays on screen. A manual refresh that fails reads Refresh failed.

Open an alert's details

1. Click the alert's row. Its details open in a panel on the right, and the selected row is highlighted.
2. To close the panel, click the row again or click the close button.

The panel shows the alert's status and name, its actions, and these fields:

If the last run failed, its error appears in red at the top of the panel.

Notify shows the Email choice from the alert's schedule. When the condition changes emails when the condition starts and stops being met; runs that repeat the same result send nothing. On every matching run emails on every run that meets the condition. See Set the schedule and when emails go out.

A role in Recipients reaches everyone who holds it at the time of the run. A deactivated or deleted role, or a deactivated or deleted person, appears struck through. A role reaches nobody, and a person is skipped when the email is sent. Hover over the name to see the reason.

Run an alert now

1. Open the alert's details.
2. Click Run now.
3. Read the message that appears: Triggered - email sent, Triggered - no email, Condition not met - email sent, Condition not met - no email or Run failed: followed by the reason.

Run now is a real run. It updates Status, Last Run and Recent runs, and emails under the same rules as a scheduled run. It does not change Next run. It runs the query as the role in Runs as. On a paused alert, it runs once and the alert stays paused. Run now is disabled while the run is in progress.

Pause or resume an alert

1. Open the alert's details.
2. Click Pause. The status changes to Paused.
3. To restart the alert, click Resume.

A paused alert does not run on schedule, even if Next run still shows a time. Resume schedules the next run from the moment you click it. Runs missed while the alert was paused are skipped. After Resume, the status returns to the condition the alert last showed, or to Error if its last run failed. Pause and Resume are disabled while the change is being applied.

Edit an alert

1. Open the alert's details and click Edit. The editor opens over the list.
2. Change what you need. Click Test to check the result. Test runs the query as the role in Runs as, so you see what the schedule will read.
3. Click Save.

Changing the query, the Runs as role or the rules resets the alert to Pending and clears Last Error. A paused alert keeps its status. Changing only the schedule recalculates Next run. When someone else edits your alert, you remain its owner. The editor leaves out recipients who are deactivated or deleted, so saving removes them from the alert.

Delete an alert

1. Open the alert's details and click Delete.
2. In the Delete alert dialog, click Delete. The confirmation reads Alert deleted.

Check run history

Recent runs in the details panel lists the 20 most recent runs, newest first, and refreshes on its own. An alert that has never run shows Not run yet. Each run shows its outcome (OK, TRIGGERED or ERROR), when it started, whether it was Scheduled or Run now, an envelope icon if recipients were emailed, the rows and duration, and any error. When there are more than 20 runs, the heading reads "Recent runs (latest 20 of N)". Runs are kept for one year.

Find out why an email did not arrive

1. Open the alert's details and read Recent runs. A run that emailed recipients has an envelope icon. If the run that met the condition has no icon, no email went out for it.
2. Check Recipients. If every recipient is struck through, nobody is emailed.
3. Check Notify. With When the condition changes, a run that repeats an earlier result sends nothing.
4. Open Admin > Notifications and check that a default email channel is set. Without one, no email is sent and nothing is logged.
5. Open Observability > Logs > Notifications and look for rows with the source Alert. A row marked Failed or Partial shows that the send did not fully succeed.

For how to set the default channel, see Notifications.

Permissions

The presets Others Alerts Viewer and Others Alerts Manager bundle these permissions. See the Permission reference. Run now, Edit, Pause, Resume and Delete appear only when you hold the permissions for them. While you impersonate another user, you cannot create, edit, run, pause or resume alerts (Impersonate a user).

Limits and edge cases

• A failed run sets the status to Error, shows the reason in Last Error and sends no email. The alert remembers the condition it last showed, so with When the condition changes, the first successful run after the fix emails only if the condition has changed since then.
• A successful run clears Last Error.
• If the platform was unavailable when an alert was due, the alert runs once when the platform is back, not once for each missed time.
• If every recipient is deactivated or deleted, runs still happen, but nobody is emailed.
• Deleting a role also deletes the alerts that run as that role.
• If an action is refused, for example because the alert changed in another tab, or because you are impersonating another user, the message and what to do are in Observability troubleshooting.
• If the alert's details, its recipient list or its run history fails to load, the panel shows Failed to load the alert, Failed to load the recipient roles or Failed to load the run history. Open the alert again from the list.

Questions, answered

My alert shows Error. What do I do?

Read the red message at the top of the alert's details. Edit the query, role or rules, and save. Saving clears the error and resets the alert to Pending until the next run.

The alert is Triggered, but nobody got an email. Why?

Usually, the run that found the condition met was not the one that started it. With When the condition changes, repeated runs send nothing. Other causes are that every recipient is deactivated or deleted, no default email channel is set, or the send failed. Follow the steps in Find out why an email did not arrive.

Does Run now change the schedule?

No. It runs and emails under the same rules as a scheduled run, and Next run stays as it was.

I changed the query and got an email again, although the data did not change. Why?

Changing the query, the Runs as role or the rules resets the alert to Pending. The next run that meets the condition counts as a new trigger, so it emails again.

Am I the owner after I edit a colleague's alert?

No. The owner stays the person who created the alert.

Why can't I see my colleague's alerts?

You see only the alerts you own, unless you hold View Everyone's Alerts. Ask an administrator for that permission, or for the preset Others Alerts Viewer.

What happens to runs missed while an alert was paused?

They are skipped. When you click Resume, the next run is scheduled from that moment.

Can I restore a deleted alert?

No. A deleted alert stops running and disappears from the list. Create it again if you need it.

Why is a name in Recipients struck through?

That person is deactivated or deleted, so they are skipped when the email is sent. A struck-through role reaches nobody. Hover over the name to see the reason.

Why can't I see the New alert button?

New alert appears only when you can create alerts. You need Create Alerts or Notify Others With Alerts. Ask an administrator for one of them, then see Create an alert.