Business Logic and Process Automation32% of the exam
Flow fault paths, debugging and run monitoring
What happens when a flow fails with and without a fault path, who gets the error email, how to debug safely and as another user, and which tools show trigger order, dependencies, version changes and run health.
Maintain, monitor, and troubleshoot flows.
~8 min read · 14 practice questions ·
What the exam expects
- Predict what a user sees and what is rolled back when a flow element fails, with no fault path or with one, for record-triggered, screen and autolaunched flows.
- Use Custom Error and Roll Back Records in fault paths, and log failures against the interview GUID.
- Route flow error emails and apply the troubleshooting checklist, including shared CPU limits.
- Debug safely: rollback mode, debugging as another user, Debug versus Test Mode.
- Pick the monitoring tool: Flow Trigger Explorer and trigger order, Compare Versions, the Usage tab, Element Error Rate and on-canvas run data.
Key terms: fault path (the connector an element follows when it fails); unhandled fault (a failure with no or an empty fault path); flow interview (one running instance of a flow); interview GUID (the identifier every interview has); trigger order (1-2,000 value that sequences record-triggered flows); rollback mode (a debug option that undoes the run's changes).
Key facts
Record-triggered flow, no fault path
- Detail
- Change blocked and rolled back; a validation rule's message replaces the generic one
Screen flow fault path
- Detail
- Completion message if no Screen; rollback only with Roll Back Records
Custom Error element
- Detail
- Record-triggered flows only
Error email recipients
- Detail
- Last modifier of the flow, or Apex exception email recipients
Interview identifier for logs
- Detail
- GUID; Salesforce ID only once paused
CPU time limit
- Detail
- Shared with all automation in the transaction, including Apex triggers
Debug as another user
- Detail
- One-time admin setup; sandboxes only
Trigger order range
- Detail
- 1 to 2,000; ties alphabetical by API name
Sources for this section (5)
- Default Flow Error Handlinghelp.salesforce.com (opens in a new tab)
- Flow Typeshelp.salesforce.com (opens in a new tab)
- Troubleshooting Flow Run Time Errorshelp.salesforce.com (opens in a new tab)
- Flow Builder Debuggerhelp.salesforce.com (opens in a new tab)
- Run Orderhelp.salesforce.com (opens in a new tab)
- Why might a flow that passes in the debugger fail during a bulk update?
- When does a screen flow fault path roll back earlier changes?
- Who can receive flow error emails?
- When do flows with no trigger order value run?
- Which tool shows the automations that call a flow before you deactivate it?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform App Builder pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform App Builder guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams