> 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.md).

# Error Tracking

Configure automated error tracking to capture unhandled exceptions, flow errors, and batch failures.

The Error Tracking screen in Pharos Admin controls the automated error collection mechanisms that give Pharos its zero-configuration observability baseline. These settings determine which types of unhandled errors Pharos captures and how frequently it scans for failures.

***

{% hint style="info" %}
For a conceptual overview of what automated error tracking captures and how it works, see [Automated Error Tracking](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md).
{% endhint %}

***

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>💻 Apex Exception Tracking</strong></td><td>Capture unhandled Apex exceptions via the error email service.</td><td><a href="https://docs.pharos.ai/configuration-guide/error-tracking/apex-exception-tracking.md">Apex Exception Tracking</a></td></tr><tr><td><strong>🌊 Flow Error Tracking</strong></td><td>Capture Flow and Process Builder errors via Process Automation Settings.</td><td><a href="https://docs.pharos.ai/configuration-guide/error-tracking/flow-error-tracking.md">Flow Error Tracking</a></td></tr><tr><td><strong>📧 Email-to-Case Error Tracking</strong></td><td>Capture Email-to-Case failures based on Support Settings and Case User configuration.</td><td><a href="https://docs.pharos.ai/configuration-guide/error-tracking/email-to-case-error-tracking.md">Email-to-Case Error Tracking</a></td></tr></tbody></table>

***

## Accessing Error Tracking Settings

From the Pharos app, open **Pharos Admin** and select **Error Tracking** from the left-hand navigation menu.

1. Open the **Pharos** app
2. Navigate to **Pharos Admin**
3. Select **Error Tracking** from the left-hand navigation menu

***

## What the Error Tracking Screen Shows

The Error Tracking page presents six configuration sections. Each section can be enabled or disabled independently via its toggle. Use the toggles to turn error tracking on or off for each mechanism as needed.

![Error Tracking configuration screen](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-88c8a6a748bc520cdf542ae0a37bb8e5ac575ee5%2Ferror-tracking-page.png?alt=media)

***

## Configuration Sections

The Error Tracking screen organizes six mechanisms. Each has a toggle and, where applicable, additional controls such as frequency or a Run Now button.

### 1. Automated Apex Exception Tracking

Tracks Apex error notices sent by Salesforce via email. Pharos generates an email alias in your org to route all Salesforce exceptions to create log records.

→ [Apex Exception Tracking](https://docs.pharos.ai/configuration-guide/error-tracking/apex-exception-tracking.md)

### 2. Event Monitoring Events Tracking

Tracks events from the Salesforce Event Monitoring app. Requires the [Event Monitoring add-on](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/monitoring/event-monitoring.md) (paid Salesforce license). When enabled, Pharos captures additional event types—such as Apex exceptions, Lightning errors, and API activity—that extend beyond automated error tracking. Configure which events to capture and set per-hour limits in **Pharos Admin → Monitoring → Event Monitoring**.

→ [Event Monitoring](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/monitoring/event-monitoring.md) | [Configuration: Events](https://docs.pharos.ai/configuration-guide/monitoring/events.md)

### 3. Automated Flow Error Tracking

Routes flow and Process Builder errors through Apex exception emails so Pharos can capture them. This setting updates Process Automation Settings to ensure flow errors are sent to the same recipients as Apex exceptions.

→ [Flow Error Tracking](https://docs.pharos.ai/configuration-guide/error-tracking/flow-error-tracking.md)

### 4. Automated Email-to-Case Error Tracking

Captures failures in Email-to-Case processing—such as parsing errors, validation rule failures, and assignment rule issues. Depending on your Support Settings and Case User configuration, Pharos updates either the Email for Automated Case User Notifications or the Automated Case User's email to route these errors to the Pharos email service.

→ [Email-to-Case Error Tracking](https://docs.pharos.ai/configuration-guide/error-tracking/email-to-case-error-tracking.md)

### 5. Batch Error Tracking

When enabled, Pharos logs errors in all failed batch jobs. Use the **Run Now** button to trigger a manual scan. Batch job failures often go unnoticed because they run during off-hours; this setting ensures they are captured and surfaced.

→ [Automated Error Tracking — Batch Job Errors](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md)

### 6. Bulk API Error Tracking

Tracks errors from Bulk API loads. Enabling this starts a scheduled process that logs bulk job failures (Data Loader operations, integration batch uploads, etc.). You can specify how frequently the process runs (default: every 4 hours). For most orgs, the 4-hour interval is sufficient—bulk loads typically don't require immediate urgency. If you just ran a data job and want to see failures right away, use the **Run Now** button to process immediately.

{% hint style="info" %}
**Changing frequency:** To change the scan frequency, you must first deactivate the Bulk API Error Tracking toggle, select the new frequency from the dropdown, then re-enable the setting.
{% endhint %}

→ [Automated Error Tracking — Bulk API Failures](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md)

***

## Exception Emails and Inbound Emails

### Exception Emails

Exception emails continue to work for users as before. Pharos adds its email service address as a recipient; it does not remove existing recipients or change how Salesforce delivers exception emails. If you want to suppress exception emails for users, you would need to update **Setup → Apex Exception Email** in Salesforce (e.g., remove user recipients). This is not recommended—exception emails are a useful backup, and Pharos captures errors without affecting their delivery.

### Inbound Emails

When an exception email arrives at the Pharos email service, Pharos creates an **Inbound Email** record for each incoming message. This record is a Pharos custom object that stores the raw email before it is transformed into a log. Inbound Emails are accessible via the **Inbound Emails** tab in the Pharos app. The tab is not visible by default but can be accessed through the Salesforce app picker.

Each Inbound Email is processed and converted into an enriched log record:

| Outcome     | Result                                                                                                                  |
| ----------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Success** | The Inbound Email is linked to the corresponding log                                                                    |
| **Failure** | The Inbound Email contains an error status; Pharos also creates an internal log (Pharos category) detailing the failure |

***

## Verifying Error Tracking Is Working

The only reliable way to confirm that exception emails are being handled is to ensure all configuration steps are complete, then verify the end-to-end flow. When exceptions occur (from normal org activity), work through these checks:

1. **Exception emails in your inbox** — Confirm you receive exception emails as expected
2. **Inbound Email records** — Open the **Inbound Emails** tab in the Pharos app (via the app picker if not visible) and confirm records are created for incoming exception emails
3. **Inbound Emails linked to logs** — Verify that Inbound Email records are linked to the corresponding log records

### If No Logs Are Appearing

If logs are not appearing after setup, work through these checks in order:

1. Confirm the running user is active ([Configuration Overview](https://docs.pharos.ai/configuration-guide/configuration-overview.md))
2. Verify the email service address is in **Setup → Apex Exception Email**
3. Check that the Quick Start wizard completed successfully
4. Review **Setup → Scheduled Jobs** for any failed Pharos jobs

***

{% hint style="warning" %}
**Sandbox Consideration:** After a sandbox refresh, error tracking configuration is reset. Run the [Quick Start](https://docs.pharos.ai/configuration-guide/quick-start.md) wizard with the **Sandbox Refresh** option to reconfigure all error tracking mechanisms.
{% endhint %}

***

## Best Practices

Apply these practices to get the most from error tracking:

| Practice                                             | Why                                                                                                                                                                 |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Enable all three core mechanisms**                 | Apex exception, flow error, and batch/Bulk API tracking each cover different failure surfaces — together they provide comprehensive baseline coverage               |
| **Keep the default scan frequency initially**        | Adjust Bulk API frequency only after observing your org's actual bulk API activity                                                                                  |
| **Check Error Tracking after every sandbox refresh** | The Quick Start wizard's Sandbox Refresh option handles reconfiguration                                                                                             |
| **Supplement with Triton for handled exceptions**    | Automated tracking only catches unhandled errors — use [Triton instrumentation](https://docs.pharos.ai/configuration-guide/advanced/triton.md) for try-catch blocks |

{% hint style="success" %}
**Next Step:** Configure [Connected Orgs](https://docs.pharos.ai/configuration-guide/connected-orgs.md) to ensure proper log attribution and enable multi-org monitoring.
{% endhint %}
