Currently for Native Salesforce nodes, only Search Records action supports error handling. However, actions such as Create or Update do not.

This in turn makes it rather risky to rely on native Salesforce nodes for critical create/update operations in a flow — if the node fails, the entire enrolment fails and no further actions execute. There's no branch-out for success/failure, no way to retry, and no error code exposed as a variable to condition on (confirmed via AFB). This is in contrast to the Send HTTP Request node, which supports a "handle failure" toggle and lets you branch instead of erroring out the whole enrolment.

This came up from a client build for SunLife (WhatsApp lead qualification journey, built in Flow Builder) — their flow relies on Salesforce record create/update as part of lead scoring, and a single failed create/update would silently kill the entire enrolment with no fallback path or retry logic. At minimum, would like: