--- title: "Using the Flow Debugger" slug: "using-the-flow-debugger" description: "Flows can span multiple systems, such as POP, IMAP, Application Servers, and Database Servers, and may or may not involve an end user. A flow can run an approval process, check or send email, handle an incident, or turn on a server. To ensure the flow runs without errors and has no performance issues, debugging is highly recommended throughout the development stages." tags: ["unit tests", "Flow", "debugger"] updated: 2026-07-23T17:15:19Z published: 2026-07-23T17:15:19Z canonical: "documentation.decisions.com/using-the-flow-debugger" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Using the Flow Debugger ## Overview The purpose of the Debugger is to ensure a Flow runs without errors. The **Flow Debugger** can be used to view how data transforms in the Flow and can be accessed from the Flow Designer. Because the Debugger runs Flows with additional processes to display contextual data for developers, the Debugger should not be used to gauge a Flow's performance. To analyze how quickly a Flow is performing and which steps may be producing bottlenecks, visit [Troubleshooting Using the Profiler](/version-10/docs/troubleshooting-using-the-profiler). --- ## Accessing the Flow Debugger The Flow Debugger can be accessed by clicking **Debug** on the top action bar of the Flow Designer. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778597833124.png) --- ## Starting the Flow Debugger When the Debugger opens, there is a large START DEBUGGING button that will initiate the debugging process with the default settings. Expanding the OPTIONS section will display additional configurations such as running a **Debug** **and** **Profile**, **Debug Only**, or **Profile Only** session. Refer to the article [Troubleshooting Using the Profiler](https://documentation.decisions.com/version-10/docs/troubleshooting-using-the-profiler) to learn more about Debug and Profile sessions. In addition, the debugging test can **Run in** **Sampling Mode,** which reduces the size of the data set by debugging only a sample of the data. This can ultimately help with performance when larger data sets are being used for testing. The last option is to **Capture as Sample Data**, which can be used to capture and store the debugging data as sample data. ### Sampling Mode: By default, the **Flow Debugger**, **Unit Tests**, and **Sample Data** are set to run in "**Sampling Mode**." In Sampling Mode, the Debugger records the data for only **five** out of all the iterations it is supposed to run. It captures the data of the first two and last three iterations, respectively. This helps reduce memory consumption and makes the debugger faster. Users can configure the sampling value and run the Flow in sampling mode for 5 to 100 iterations. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783342841122.png) ### Project-level Sampling Mode Setting A project-level setting called Flow Debug Default includes a **Run in sampling mode** option. If this is enabled, the debugger will continue to use only a sample of the data during debugging, as previously described. However, if this setting is disabled, the debugger will use all available Flow data rather than just a sample. This enhancement provides greater flexibility in processing data during debugging, allowing teams to choose between faster, memory-efficient sampling or comprehensive, full-data debugging based on their project needs. The images below illustrate the difference between debugging with sampling mode enabled and disabled. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783026274299.png) ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783026315710.png) --- ## Running the Flow Debugger Debugging Multiple TimesTo debug multiple times without needing to close the Debugger tool, Users can use Unit Tests/Sample data or click on CREATE NEW SESSION in the top left of the Debugger. After starting the Flow Debugger, there will be three tabs: **Flow** and **Dashboard.** ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778599381829.png) When Users select the **Debug and Profile** option, an additional tab called **Profile Page** will appear. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-07-22_14h23_39.png) #### Step Inspection Clicking on the steps within the Flow provides the ability to view that step's **Input Data**, **Output** **Data**, and **Step** **Info** by selecting the step. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783026375398.png) #### Flow Debugger Enhancements After a debug session completes, select a step in the debugger to view its inputs, outputs, and other debug details. Refer to the following image: ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778599755441.png) 1. **Step Execution Count**: This Panel on the left shows all the step execution iterations. If a Flow uses a For Each or For Loop step, which loops the Flow through steps and runs the step multiple times. This list shows all the iterations that the step has gone through. Users can click on any iteration to view the data for that specific iteration. 2. **Input & Output View:** This section shows all input and output data associated with the selected step. Users can copy inputs or outputs individually using the copy button in the top-right corner. The splitter between panels can be dragged to adjust the view, and a search bar allows Users to quickly find specific data within the inputs and outputs. 3. **Mappings Panel:** This panel, similar to the Step Properties panel, is read-only and displays the mapping types and data passed through the step. It helps Users understand how data is mapped and transferred within the flow. #### Sub Flows and the Debugger Sub Flows can be viewed within the Debugger. They appear underneath the Flow on the left side of the screen. Clicking on the name of the Sub Flow will show its steps on the right.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778600180904.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778600269144.png) Debug Report Page The **Debug Report Page** provides a simple Report of the steps within the Flow. This Report has been **deprecated** in **v9.14.** Users can now access the same report through the new Dashboard by switching reports via the Report Edit option. #### The Dashboard The **Dashboard** provides a snapshot of the executed Flow. The tiles on the left-hand side display the **Total Time** it took for the Flow to execute, the **Number of Steps,** the **Number of Flows,** the **Number of Rules, the Number of Flows,** and the **Number** **of** **Exceptions**. This Dashboard is displayed as a Report but can be viewed in a different form by clicking **Change Report**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-07-22_15h16_33.png) ## Flow Debugger Icon Guide | Icon | Description | | --- | --- | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1784826541254.png) | This icon appears when a Flow is run. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1784826556011.png) | This icon appears when a Rule is run. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1784826572636.png) | This icon appears when a Form is run. | #### Remember to the Recent List Setting the Remember to the Recent List checkbox in the **Edit Designer Settings** window to true will save the current run in the Debugger in the **Data Samples** back in the Flow Designer. This default option can be turned off and on in **System > Settings > Designer Studio Settings**, under the FLOW DEBUG DEFAULT category. After the Debugger runs and Remember to the Recent List is set to true, the run will be saved in the **Samples/Unit Tests** panel in the Designer. Under **Sample Data > [Flow Name],** there will be the saved version of the previously run Debugger. Each time the Debugger is run, and this option is on, it will save a new Sample Data that can be Debugged again. The magnifying glass will show what input was used for that run, and the save icon will allow the ability to save that run as a **Unit Test** or **Data Sample**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778600959424.png)