Understand Flow Failure Notification Email

Whatfix sends a consolidated email every day that contains a list of all the broken Flows in your account. You can choose to receive these daily email notifications.

When does Whatfix send the Flow Failure Notification Email?

Whatfix sends the Flow Failure Notification Email once every day. Each email contains a list of Flows that failed the previous day, along with the following information:

• Name of the failed Flows linked to Flow Analytics

• Number of times each Flow failed

• Step number at which the failures happened

• Author of the Flow

• Reason for failure

• Possible fix

• URL where the end-user ran the Flow

Note:

The Flow Failure Notification Email includes only Flows that are in the Production stage.

How does Whatfix identify a Flow failure?

Whatfix tracks user engagement with each Flow. When a Flow step fails to appear for an end user, it is marked as a failure. Events such as Failed to launch Flow step are captured to identify where the failure occurred in the application. If any step fails to load during a Flow, that step is marked as a failure, and the Flow is marked accordingly.

What are the key Events that are tracked?

The following table lists the Event names and their descriptions:

When does a Flow appear in the daily Flow Failure Notification Email?

A Flow appears in the daily Flow Failure Notification Email when the following conditions are met:

• The Flow is in the Production stage and has at least one missed step from the previous day.

• The Flow captures at least one failure event: Failed to launch Flow step or Flow backtracked 1 step and failed.

How do I receive Flow failure notification Email?

For more information on how to receive the Flow failure notification Email, see How do I receive Flow failure notification Email?

What are the benefits of the Flow Failure Notification Email?

The Flow Failure Notification Email helps you:

• Detect issues in your Flows early on and fix them.

• Prioritize which Flows need immediate attention based on user impact.

• Understand patterns of failure that suggest recurring Flow issues.