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

# Notifications

> Alert your team when a Bolt schedule succeeds, fails, or breaches its SLA, via email, Slack, or Microsoft Teams, with per-destination outcome toggles.

Notifications tell your team when a schedule succeeds, fails, or breaches its SLA. Choose one or more destinations (email, Slack, or Microsoft Teams) and pick which run outcomes trigger each one.

## SLA threshold

Set a time threshold in minutes. Paradime sends an **SLA** alert when a run has been running longer than this threshold. Only destinations with the **SLA** toggle on receive it.

## Destinations

A destination is where alerts go and which outcomes trigger them. Add as many as you need with **Add destination**, then toggle the outcomes independently for each one:

* **Success** — the run completes successfully.
* **Failure** — the run completes with errors.
* **SLA** — the run exceeds the SLA threshold while still running.

Each destination is one of:

* **Email** — any email address.
* **Slack** — a channel (requires the Slack integration).
* **Microsoft Teams** — a channel (requires the Microsoft Teams integration).

<Warning>
  To send alerts to Slack or Microsoft Teams, connect the integration first:

  * [Slack](/integrations/slack)
  * [Microsoft Teams](/integrations/microsoft-teams)
</Warning>

### Add a destination

1. In **Notification settings**, click **Add destination**.
2. Choose **Email**, **Slack**, or **Microsoft Teams**, then select the address or channel.
3. Toggle **Success**, **Failure**, and **SLA** for that destination.
4. Set the **SLA threshold** (in minutes) if any destination uses SLA alerts.
5. Click **Deploy** to save.

## Notification templates

You can fully customize the content and structure of Slack and Microsoft Teams alerts using templates. Templates are created in **Bolt → Alert Templates** and attached to a channel destination per schedule. For full details, see [Alert Templates](/products/bolt/creating-schedules/alert-templates).

## Bolt system alerts

Bolt system alerts cover system-level issues with Bolt itself, separate from a schedule's own run notifications. They are configured once for the workspace from the **Bolt System Alerts** panel, opened from the top right of the Bolt schedules homepage.

| Alert                                   | Severity | Triggered when                                                                                                |
| --------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------- |
| **Can't clone repo**                    | Critical | Bolt cannot clone your repo because your Git provider (such as GitHub or GitLab) is unavailable.              |
| **Schedule run Out-of-Memory**          | Error    | A Bolt schedule runs out of memory, for example loading too much data into memory inside a dbt™ macro.        |
| **Schedule Time-out**                   | Warning  | Your warehouse has run out of resources or is unavailable and a Bolt schedule has run for more than 24 hours. |
| **Can't read paradime\_schedules.yaml** | Warning  | There is an error in `paradime_schedules.yaml` and Bolt cannot read the file.                                 |

Then choose where these alerts go. You can set one Slack channel and one email destination for system alerts:

* **Slack channel** — the single channel that receives system alerts. Click **Refresh** to reload the channel list.
* **Email notifications** — a single email destination for system alerts.

<Info>
  Bolt system alerts are workspace-wide and independent of a schedule's own [notification destinations](#destinations). Set them up once from the Bolt schedules homepage.
</Info>

<Card title="Define this as code" icon="code" href="/products/bolt/creating-schedules/schedules-as-code/configuration-reference#notifications-configuration" horizontal>
  Configure the `notifications` block (emails, Slack, Microsoft Teams) and `sla_minutes`.
</Card>


## Related topics

- [Notifications](/products/settings/configuration/notifications.md)
- [Setting Up Notifications](/guides/paradime-101/running-dbt-in-production-with-bolt/setting-up-notifications.md)
- [Workspaces and data mesh](/guides/paradime-fundamentals/workspaces-and-data-mesh.md)
- [Configuration Reference](/products/bolt/creating-schedules/schedules-as-code/configuration-reference.md)
- [Test Code Changes On Pull Requests](/products/bolt/creating-schedules/templates/ci-cd-templates/test-code-changes-on-pull-requests.md)