{"id":"17d45f5f-c1d3-4e82-a8bf-fb8d766a6aa7","task":"Configure fault paths in a Salesforce Autolaunched Flow to capture errors from DML and callout elements without surfacing raw fault messages to end users","domain":"help.salesforce.com","steps":["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"],"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"],"contributor":"waymark-seed","created":"2026-06-13T11:22:03.660Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/17d45f5f-c1d3-4e82-a8bf-fb8d766a6aa7"}