Flow errors only

A Flow errors only environment needs no connection, no integration user and no package in the client org. The client admin makes two Setup changes, and Salesforce’s own Flow error emails do the rest. Each email becomes an incident within seconds.

What you need from the client

• The client org’s ID, 18 characters. The admin finds it in Setup > Company Information. The app uses it to check that each email comes from that org.

Set it up

1. In Manage clients > Add client, choose Flow errors only and enter the org ID. The app creates a private address for this environment and shows it with a copy button.
2. The client admin makes two changes in their org:
   1. Setup > Apex Exception Email: add the address.
   2. Setup > Process Automation Settings: set Send Process or Flow Error Email to to Apex Exception Email Recipients, and save.

Check the second change. By default, Salesforce sends Flow error emails to whoever last edited the Flow, so the first change alone catches nothing. We have seen this setting fail to save. Ask the admin to reload the page and check it.

Until the first real Flow error email arrives, the environment shows Routing not yet confirmed.

What you get

• An incident for each failing Flow, with the Flow, the element that failed, the error code and the error text with personal data removed. Repeats add to the same incident.
• Alerts by email and Salesforce notification to the consultants assigned to the client.
• Last email received in place of a collection time. No emails could mean everything is fine, or that the routing has broken. After 30 days with nothing, the app reminds you to check the routing.

Incidents are labelled Reported by email, not verified through the API, because there is no connection to confirm them. One with no repeat emails for 7 days resolves itself.

What you don’t get

Limits, logins, jobs, Health Check and Setup changes need a connection. They are hidden for Flow errors only environments, so you never see an empty panel that looks healthy.

Moving to full monitoring

In Manage clients, choose Switch to Full on the environment. The Add client window opens at the client setup step, with the same three ways to connect a client. Flow errors only monitoring carries on until the connection test passes. Then the environment switches to full monitoring. It keeps its Flow error address, so the client admin changes nothing in Apex Exception Email, and its incidents stay. The next check confirms them through the API, as it does for any Flow error email.