Save Successful Record Changes in a Batch from Failed Actions in Processes and Flows

Processes and flows now save successful record changes from failed actions that support partial save. Previously, if one record in a batch failed to save from an action, the entire batch rolled back. Now, Salesforce rolls back only the records that fail to save.

Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

Why: If an error occurs while executing an action from processes or flows, Salesforce attempts to save all successful record changes in a batch.

Salesforce handles errors in processes and flows differently depending on whether the associated action follows the "all or nothing" rule.
  • If a record fails to save due to an action that follows the all or nothing rule, the entire transaction rolls back.
  • If a record fails to save due to an action that uses partial save, we attempt the remaining actions in the bulk operation up to three times.

Here's a summary of how processes and flows save records in batches from actions.

Process Builder Action How Are Records Saved
Apex Depends on code
Create a Record Partial save
Email Alerts All or nothing
Flows (Create Records and Update Records elements only) Partial save
Flow (other elements) All or nothing
Post to Chatter All or nothing
Processes Partial save
Quick Actions All or nothing
Quip All or nothing
Send Custom Notification All or nothing
Submit for Approval All or nothing
Update Records Partial save
Flow Builder Action How Are Records Saved
Apex Action Depends on code
Email Alert All or nothing
Post to Chatter All or nothing
Quick Action All or nothing
Send Custom Notification All or nothing
Submit for Approval All or nothing
Subflow Partial save
Create Records Partial save
Update Records Partial save
Flow (other elements) All or nothing