> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/email-notifications-for-failed-process-flow-runs.md).

# Email notifications for failed process flow runs

## Introduction

You can configure a process flow to trigger email notifications in the event that a process flow runs and fails. This is a two-stage process:

* [Add the required email recipients to a notification group](/product-documentation/general-settings/notification-groups.md#adding-a-new-notification-group)
* [Update settings for your process flow(s)](#updating-process-flow-settings-to-trigger-failed-run-notifications)

{% hint style="info" %}
If you're not sure how to approach a process flow that's failed, see our [Process flow run failures](/product-documentation/process-flows/troubleshooting-process-flows/process-flow-run-failures.md) troubleshooting guide.
{% endhint %}

## Need to know

Email notifications for a failed process flow run are only sent if:

* the process flow is [enabled and deployed](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md)
* the process flow is initiated via the [trigger shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md) (i.e. not for manual runs)

## Updating process flow settings to trigger failed run notifications

Having [added email recipients to a notification group](/product-documentation/general-settings/notification-groups.md#adding-recipients-to-a-notification-group), you should access settings for the required process flow(s) and apply this group to the **email failure notifications** section. To do this, follow the steps below.

**Step 1**\
[Access the process flow](/product-documentation/process-flows/accessing-your-process-flows.md) that you want to update.

**Step 2**\
Click the 'cog' icon in the [canvas](/product-documentation/process-flows/building-process-flows/the-process-flow-canvas.md) toolbar to access general settings for this process flow:

<div align="left"><figure><img src="/files/DLY0lkRywEDu27Li5bI4" alt="" width="233"><figcaption></figcaption></figure></div>

**Step 3**\
From the **settings** panel, click in the email failure notifications field and select the appropriate  group to receive an email notification in the event that this process flow runs and fails:

<div align="left"><figure><img src="/files/Rpxwt5sEH138Ho0AGLub" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
All defined notification groups are available for selection. If you need to add a new group or check recipients in an existing group, please check our [Notification groups](/product-documentation/general-settings/notification-groups.md) page.
{% endhint %}

**Step 4**\
Save changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/email-notifications-for-failed-process-flow-runs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.