Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Debug More Flows Faster
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Why: If you use rollback mode when you debug a flow, Flow Builder rolls back changes that the flow makes to the database after the flow finishes. Flow Builder rolls back indirect database changes too. For example, a flow updates a child record that causes an Apex trigger to fire and to update the parent record. The update to the parent record is also rolled back.
- Available for autolaunched flows.
- Non-DML statements, such as HTTP requests, are executed and are not rolled back.
- Asynchronous actions and asynchronous DML statements are not rolled back.
- The Pause element and some actions don’t support rollback mode. If you debug a flow with one of those elements or actions, the flow stops before executing the element or action. All DML statements that executed before the element or action are rolled back.
When you debug a schedule-triggered flow that runs for a batch of records, Flow Builder uses the oldest record that matches the filter conditions.
The Lookup component makes it easy to set values for record variables.
How: To use rollback mode when you debug an autolaunched flow, click Enable rollback mode.