Debug More Flows Faster

When you debug an autolaunched flow that saves changes to the database such as create records, you don’t have to revert those changes manually anymore. In Flow Builder, use rollback mode and let it save you the hassle. You can now use the debug option in Flow Builder for schedule-triggered flows. And the debug option includes the Lookup screen component so that you can set record variables more easily.

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.

Considerations for rollback mode:
  • 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.

Debug the flow window with the Lookup component highlighted

How: To use rollback mode when you debug an autolaunched flow, click Enable rollback mode.

Debug options section of the Debug the flow window