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

# How alerts work

> When Expira sends expiry alerts, who receives them, how thresholds, catch-up, retries and the monthly alert limit work.

Expira checks every asset once a day at **08:00 UTC** and sends alerts for anything due. Configure alerts under **Alerts → Delivery**.

## Team and personal settings

**Alerts → Delivery** has one tab per scope:

* **Personal:** for your private assets. You can always change it.
* **One tab per team** you belong to: for that team's assets. Team **maintainers** and organisation **owners and admins** can change it; other members can only view it.

Each tab has two parts:

* **Alert preferences:** how early to alert, and through which channels.
* **Delivery channels:** the [email](https://docs.expira.dev/alerts/email.md), [Slack](https://docs.expira.dev/alerts/slack.md), [Discord](https://docs.expira.dev/alerts/discord.md) and [webhook](https://docs.expira.dev/alerts/webhook.md) channels for that scope.

## When an alert fires

Pick one or more thresholds under **Alert at**: **30, 15, 7 or 1 day** before expiry. Then pick the channels under **Via** and press **Save preferences**.

Until a team or person saves preferences, Expira alerts by email at 30, 15, 7 and 1 day, as long as an email channel is connected and on.

* **One alert per threshold.** An asset with 30, 15, 7 and 1 days set gets up to four reminders before it expires.
* **Catch-up after a missed day.** If a run is missed, the next run sends the nearest threshold that's due, so you get one late reminder instead of none.
* **One more alert after expiry.** If an asset expires without being renewed, Expira sends one "expired" alert, within 7 days of the expiry date.
* **Renewing starts over.** When an asset's expiry date moves forward, the thresholds start again for the new date.

## Who receives alerts

| Asset | Channels used | Email recipients |
| - | - | - |
| Team asset | That team's channels | Active members of the team |
| Private asset | Your personal channels | You |
| Team asset with no team | Email only | Organisation owners and admins |

A **paused** channel sends nothing. Email is only sent when the scope has an email channel connected and on.

## Failed and skipped alerts

* **Failed** sends are retried on the next daily runs, up to **3 attempts** in total.
* **Skipped** alerts (for example when the monthly limit is reached, or no channel is set up) are checked again on the next run, so fixing the cause recovers them.
* Each run, organisation owners and admins get **one summary email** listing the alerts that couldn't be delivered.

Every alert, with its status and any error, is listed under [Alert history](https://docs.expira.dev/alerts/history.md).

## Monthly alert limit

Each plan includes a number of alerts a month (Starter 50, Pro 2,000, Scale 20,000). Every delivery counts once, on any channel: one email to a whole team is one alert, and one Slack message is one alert. The count resets on the 1st of each month (UTC). Alerts past the limit are skipped and sent once there's room again. See [Plans and limits](https://docs.expira.dev/account/plans.md).


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