---
schema_version: "1"
id: b35951835593b301c525cc959db3acc3b95cec8611a4794ded402bbfb492a0b7
title: Flow Testing and Debugging
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_automate_flow_debug.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_debug.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b1ddd93127ffc3838e9406dbef286f5730f165210e671a0654edefe26271a862
description: Save debug configurations when you save changes to a flow. Reuse tests from old flow versions.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Flow Testing and Debugging

Save debug configurations when you save changes to a flow. Reuse tests from old flow versions.

- **[Retain Debug Configurations Within Flow Editing Sessions](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_debug_setup_debug_values_persist.htm&release=260&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_debug_test_versions.htm&release=260&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_test_isolated_test_data.htm&release=260&type=5)**  
    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.

#### See Also

- [_Release Notes_: Test Multiple Records in Segment-Triggered Flows in Debug](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_debug_multiple_individuals.htm&release=260&type=5 "Test up to 10 records simultaneously. Use the debug panel to instantly verify how different customers move through your flow. This update helps you quickly identify issues across diverse customer profiles before activation.")
- [_Release Notes_: Control Path Selection When Debugging Path Experiments](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_debug_path_experiment.htm&release=260&type=5 "Configure the Path Experiment element to randomize path assignment or manually select a winning path while debugging. Randomization is the default, but you can validate specific paths without relying on chance by using manual selection. With the manual selection configuration, you can test the exact path you want to validate.")
- [_Release Notes_: Personalize and Debug On-Demand Flows with Apex](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_on_demand_flow.htm&release=260&type=5 "Personalize on-demand flows with Apex code and control processing priority when triggering flows via API. Select specific individuals and contact points to target messages. Debug flows with built-in debugging tools to test logic and identify issues before activation. Access help documentation from the start node to understand configuration options and best practices. These updates provide more flexibility for customizing flow behavior and faster troubleshooting during development.")