---
title: Alert Notifications
slug: blueprint/alert-notifications
createdAt: 2026-11-06T22:01:54.232Z
---

Alert notifications are emails Blueprint sends when a Flow Activity alert activates on a Flow. Use them to learn that a Flow needs attention without opening Blueprint.

For the checks that raise alerts, see [Flow Activity Settings.](docId\:Pzyo3nFnI6uFl8gHkZP5i). For when alerts activate and clear, see **[Alert History and the Needs Attention Indicator](docId:75aUZSK98PLhtUjmw_VLr)**.

***

# Prerequisites

Blueprint sends alert emails only when the following are in place:

- Outgoing mail is configured. See **[Email Settings](docId:1yuluSxMHbA2e-FqwbCYd)**. 
- The Flow or its environment has at least one recipient. With no recipients, email alerting is off.
- Each recipient has an email address.

***

# Recipients

Blueprint emails two recipient lists for each Flow:

| **List**              | **Where you set it**                                                            | **Covers**                     |
| --------------------- | ------------------------------------------------------------------------------- | ------------------------------ |
| **Flow recipients**   | **Validate** -> **Flow Activity** -> **Settings** on the Flow                   | that Flow only                 |
| **Global Recipients** | the **Default Recipients** column of the Environments table in the Admin Portal | every Flow in that environment |

- Both lists show each recipient by user name. Hover a name to see the email address.
- The **Default Recipients** count shows 0 when an environment has no default recipients.

To add recipients to a Flow:

1. Open the Flow and go to **Validate** -> **Flow Activity** -> **Settings**.
2. Add users or Blueprint Groups in the recipients field.
3. Click **Save changes**.

To set an environment's default recipients:

1. In the Admin Portal, go to **Settings** -> **RPA Management** -> **ALC**
2. In the Environments table, click the count in the **Default Recipients** column.
3. Add or remove users in the popup dialog. 

For the Environments table, see **[ALC](docId:0Qtv6AzAaN_MlY2MTj9v8)**.

***

# When Emails Are Sent

Blueprint sends an email when an alert activates. This includes alerts that activate during Dataverse Synchronization, Flow Import and the nightly job.

Blueprint sends no email when an alert clears, including when you turn its check off. It sends no reminders while an alert stays active.

***

## Notification Off Pill

The **Notification off** pill shows when email alerting is off because there are no recipients. 

- On a Flow's **Flow Activity** tab, it shows when the Flow has no recipients. 
- On the **Tools** -> **Flow Activity** page, it shows when the environment has no default recipients.

**Note:** Alerts still activate and appear in Alert History while the pill shows. See **[Alert History and the Needs Attention Indicator](docId:75aUZSK98PLhtUjmw_VLr)**.

***

# Troubleshooting

If an expected email did not arrive, open the Flow's **Alert History** sub-tab and look for the alert. Blueprint writes a row when an alert activates, so no row means no email was due.

If there is no row:

- Open the **Settings** sub-tab and make sure the check is switched on under **Alert Types**. See **[Flow Activity Settings](docId\:Pzyo3nFnI6uFl8gHkZP5i)**.
- Look for a Dataverse sync banner on the **Flow Activity** tab. Some checks pause while sync is down. See **[Flow Activity](docId\:HyqDjvPWb8LB5Bz9DsuVB)**.

If there is a row:

- Compare its **When** time with the time you added the recipient. Blueprint emails only at activation, so a recipient added later gets no email for that alert.
- Look for the **Notification off** pill. If it shows, add recipients to the Flow or its environment.
- Hover each recipient's name to check the email address.
- Check that outgoing mail is configured in **Email Settings.**