Error Monitoring

Monitor Salesforce runtime errors — flow failures and Apex exceptions — from every registered org, in one place.

Observe > Error Monitoring collects the runtime errors your Salesforce orgs report — flow failures and Apex exceptions — across every org registered with codev, and shows them on one dashboard. It is tenant-wide: the page covers all registered orgs, not one project.

Error Monitoring — errors across registered orgs, with the trend over the selected time range.

The time range selector covers the last hour up to the last 30 days. The summary shows three counters — total errors, flow failures, Apex exceptions — the error trend over the range, and a per-org breakdown. Click an org row to drill into its errors.

How errors reach codev

Salesforce itself sends the errors — codev does not poll your orgs. Each tenant has a secure ingestion email address, and you register it in the org as an error recipient:

1. Copy the ingestion address — the page shows it, with the steps, whenever an org has not sent anything yet.
2. In Salesforce Setup, open Apex Exception Email and add the address with Add Non Salesforce User.
3. For flow errors, in Process Automation Settings set Send Process or Flow Email To to Apex Exception Email Recipients.

From then on, every unhandled Apex exception and flow failure the org emails is parsed and appears on the dashboard, attributed to the org that sent it.

Drilling into an org

The per-org view lists each error with its time, type, message, and component. Expand a row for the full record — exception type, Apex class and method or flow, the impacted user, the message, and the stack trace. Copy error details copies the record for sharing in a ticket or a chat.

The per-org error list — expand a row for the full detail, including the stack trace.

Filter by error type, search across messages, and adjust the time range — the search covers the selected range.