> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/best-practices/enable-failure-notifications.md).

# Enable Failure Notifications

Your workflow may experience an error, it happens and it can be fixed. Turning on your failure notifications allows you to stay on top of any errors and troubleshoot them quickly. Failure can occur for multiple reasons and the [Logs will give more details on each failure](/workflow-activity/logs.md).

Also, you don't have to be in the troubleshooting business alone! Notifications can be sent to several team members by adding their email addresses to the workflow's notifications settings.

You can turn on **Notifications** and add emails in the **Dashboard** tab of your workflow. Either select the notifications box to the right of your workflow activity or **Manage Workflow**. On the Notifications tab, turn on notifications and enter the email addresses to be notified.

![Catch those workflow gremlins with notifications.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FtpYHxOwp1K7cQt4akTpo%2Fas-notify.png?alt=media\&token=942e9bce-9154-44a6-85dd-117a81228e69)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getmesa.com/best-practices/enable-failure-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.