Configure fault paths in a Salesforce Autolaunched Flow to capture errors from DML and callout elements without surfacing raw fault messages to end users
For every Create Records, Update Records, or HTTP Callout element in the flow, draw a Fault connector to a dedicated error-handling subpath
In the fault path, add an Assignment element to copy {!$Flow.FaultMessage} into a text variable for logging
Add a Create Records element on the fault path to write an Error_Log__c record with the fault message, triggering record Id, and a timestamp
Optionally add a Send Email or Custom Notification element to alert an admin when a fault occurs in production
Connect the fault path to an End element rather than looping back to avoid infinite fault recursion
Test fault paths by temporarily configuring a callout element to point to an invalid endpoint so the fault fires during debug runs
Known gotchas
If a fault path itself contains a failing DML element and that element has no fault connector, the entire flow interview fails with no error logging — always add fault handling to error-path DML too
Fault paths in Autolaunched Flows run in the same transaction; a fault that occurs after successful DML operations earlier in the flow does not roll back those earlier operations unless you explicitly throw an exception in Apex
The {!$Flow.FaultMessage} is truncated at a platform-defined character limit; for callout faults, the HTTP response body may not be fully included
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp