---
title: "Why do I get Flow Failure email even when the Flow is running properly?"
slug: "why-do-i-get-flow-failure-email-even-when-the-flow-is-running-properly"
updated: 2025-05-29T04:49:04Z
published: 2025-05-29T04:49:04Z
---

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

# Why do I get a Flow Failure email when the Flow is running properly?

A Flow Failure notification might appear for a Flow. However, when you check the Flow, it seems to work correctly. Flow failures occur only when a user attempts to run the Flow and it fails at the reported step.

This situation can arise due to the following reasons:

- The end user lacks the necessary role or [permissions](/studio/docs/whatfix-user-roles)to see the UI elements on which the Flow is created. For example, the end user with the translator role cannot view the account management page, causing any Flow created on that page to fail for that end user.
- A Flow created across multiple pages might fail if the necessary conditions to redirect to the URL are not met and the page on which the Flow is supposed to continue doesn't load. For example, if you create a Flow that opens on a page that end users can only access by logging in, but they haven't signed up, the Flow fails for them.
- The application UI where the Flow step is created might differ from the UI where the Flow is played. For example, the end user might have access to a different [dashboard](/studio/docs/common-best-practices), and not the one where you created and tested the Flow.

## Related

- [Flow Failure Reason - Step not created](/flow-failure-reason-step-is-not-created-on-the-currently-opened-page.md)
- [Flow Failure Reason - Display rules failed](/flow-failure-reason-display-rules-failed.md)
- [Flow Failure Reason - CSS Selector failed](/flow-failure-reason-css-selector-provided-for-the-step-failed-to-find-the-element.md)
- [Flow Failure Reason - Element could not be found](/flow-failure-reason-element-could-not-be-found.md)