> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/error-tracking/flow-error-tracking.md).

# Flow Error Tracking

How Pharos captures Flow and Process Builder errors by configuring Process Automation Settings.

Flow and Process Builder errors do not automatically go to Apex Exception Email recipients. By default, Salesforce sends flow error notifications to the flow owner or runs them through a separate notification path. Pharos needs these errors to be routed through the same exception email pipeline so they can be captured.

***

## Process Automation Settings Updates

**Process Automation Settings** (Setup → Process Automation Settings) control where Salesforce sends flow error notifications. When you enable **Automated Flow Error Tracking** in Error Tracking, Pharos updates the **Send Process or Flow Error Email to** setting so that flow and Process Builder errors are sent to the Apex Exception Email recipients. This ensures that when a flow fails—whether it's a screen flow, record-triggered flow, or autolaunched flow—the error notification is routed to the Pharos email service, which parses it and creates a log record.

Without this setting, flow errors either go to a different default destination (such as the flow owner) or may not be sent at all, leaving them invisible to Pharos.

### Locating the Setting

In Salesforce Setup, go to **Process Automation Settings**. In the **Flow Error Email Configuration** section, find the **Send Process or Flow Error Email to** dropdown. Pharos sets this to **Apex Exception Email Recipients** so that flow error emails are routed through the same pipeline as Apex exceptions.

![Process Automation Settings — Send Process or Flow Error Email to](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-5f5b1aec38df6c9cacb5b8a17cdc5a9fca9f14fe%2Fprocess-automation-settings.png?alt=media)

***

## The Default Setting Problem

Salesforce's default Process Automation Settings often do **not** send flow errors to Apex Exception Email recipients. Many orgs leave this unchanged, which creates a visibility gap.

When flow errors are not routed to exception email recipients:

* Flow failures are not captured by Pharos
* Admins and developers lack visibility into declarative automation failures
* Errors may only surface when users report issues or when someone manually checks flow run history

{% hint style="warning" %}
**Default is a bad practice:** Leaving the default unchanged when using Pharos means flow failures go uncaptured. Enable Flow Error Tracking to capture flow failures alongside Apex exceptions and batch job errors.
{% endhint %}

***

## What Gets Captured

The email service captures flow and Process Builder errors once they are routed to Apex Exception Email recipients. Each flow type contributes similar details to the log record.

| Flow Type                  | Captured Details                                                    |
| -------------------------- | ------------------------------------------------------------------- |
| **Screen flows**           | Flow name, version, failed element, variable values, execution path |
| **Record-triggered flows** | Flow name, version, failed element, variable values                 |
| **Autolaunched flows**     | Flow name, version, failed element, variable values                 |
| **Process Builder**        | Process name, failed element, variable values                       |

Pharos presents flow errors with an interactive visual debugger showing the execution path and failure point—transforming cryptic error emails into clear diagrams.

### Fault Path Limitation

When a flow has a fault path (fault connector) and an error is directed there, the fault is considered **handled**. Salesforce still sends flow error emails for these cases, but Pharos deliberately does not capture them—handled errors are expected behavior that the flow designer has accounted for, not unhandled failures requiring attention.

If you need visibility into errors that are handled by fault paths (e.g., to track how often a flow takes the fault branch or to alert on specific fault scenarios), use [Triton instrumentation](https://docs.pharos.ai/configuration-guide/advanced/triton.md). Add an Apex action in the fault path that calls the Triton logger to create a log. You can then apply rules, notifications, and reporting to those logs.

{% hint style="info" %}
**Related:** [Automated Error Tracking — Flow Failures](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md) | [Flow and Process Builder Logs](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/flow-and-process-builder-logs.md) | [Triton](https://docs.pharos.ai/configuration-guide/advanced/triton.md)
{% endhint %}
