Observability: errors & limits

Observability shows what goes wrong in your orgs after a release: unhandled Apex exceptions, failing flows, and org limits running out. Pick the org at the top right.

#Flow and Apex errors

Salesforce emails every unhandled Apex exception and every flow failure. Diffbridge reads those emails for you.

1. Copy the org's inbound URL from the Errors tab.
2. In your email provider, create an inbound route that POSTs incoming mail to that URL: SendGrid Inbound Parse, Mailgun Routes (forward), Postmark Inbound. A plain JSON body with subject and text works too.
3. In Salesforce, send the error emails to that inbound address:
   • Setup → Apex Exception Email: add the address.
   • Setup → Process Automation Settings: Send Process or Flow Error Email to → Apex Exception Email Recipients.

Each email is parsed into the class or flow, the method or flow element, the exception type, the message, the stack trace and the user. Repeats of the same error (with different record IDs or numbers) are grouped.

The Errors tab shows a daily chart (Apex and flows), and the groups: how often, how many users, first and last seen. Open a group for the stack trace and every occurrence.

• Root cause hint: when a group first appeared after a deployment that changed that class or flow, it says Started after the deployment from … with a link.
• Create ticket files a Jira bug (in the first project key of the Jira integration) or an Azure DevOps bug with the details, and links it on the group. See Integrations.
• Alerts: New Flow/Apex error when an error is seen for the first time, and Error spike when more than a set number arrive within a set number of minutes (default 20 in 10). Choose them per channel under Settings → Notifications.

In demo mode, Simulate errors adds a realistic burst of Apex and flow errors.

#Org limits

The Org limits tab shows each limit's usage: daily API requests, data and file storage, async Apex executions, Bulk API batches, platform events, emails, and the rest of Salesforce's limits.

Diffbridge checks every hour (turn Hourly checks off to stop) and keeps 30 days of history. You're notified (Org limit running out) when a limit passes the warning level (default 80%), and again when it passes critical (default 95%). Check now refreshes immediately.