Save debug configurations when you save changes to a flow. Reuse tests from old flow versions.
- Retain Debug Configurations Within Flow Editing Sessions
Preserve debug configurations when you save changes to your flow. Debug inputs such as triggering record values, debug options, and input variable values now remain set when you save flow changes within your Flow Builder session. Refreshing your browser or closing Flow Builder clears all debug settings. To clear debug settings manually, click Reset Debug Settings. - Assign Flow Tests to Specific Flow Versions for More Control
Reuse tests from previous flow versions if the scenario still applies to a new version. Align flow tests precisely with each flow version so updates don’t cause incorrect results from other flow versions. - Test Record-Triggered and Autolaunched Flows with Isolated Test Data
Run flow tests without affecting your org’s data. Use isolated test data with Apex Test Setup in record-triggered and autolaunched flows, and Set Test Input Values for autolaunched flow variables. Flow tests require predictable data. When you use org data for testing, anyone can change that data and your tests can start to fail. Record IDs differ between sandbox and production, so tests that pass in one environment can fail when you deploy to another. We added a way to create isolated test data when the test runs, just like Apex Test Setup creates data at run time. Your flow test data stays consistent so you can deploy it across environments. Isolated test data is available only for record-triggered and autolaunched flows.