---
sourceDocument: Brazil Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Flow debugger

# Flow debugger {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Flow Debugger

The Flow Debugger in Workflow Studio allows ServiceNow customers to debug flows and subflows efficiently using a dedicated tab.
It enables setting breakpoints, pausing execution, stepping through flows line-by-line, and reviewing both configuration and runtime values.
This tool helps validate flow behavior and troubleshoot issues without modifying the actual flow configuration.
Show full answer Show less  

## Key Features

* **Dedicated Debugging Interface:** Access a debug mode tab from the Workflow Studio home page to view flow execution details and control flow execution.
* **Breakpoint Management:** Set and remove breakpoints on flow steps to pause execution at critical points for inspection.
* **Step Controls:** Step into subflows, step out to parent flows, step over breakpoints, skip all breakpoints, and resume paused flows for flexible navigation through the flow execution.
* **Action Details Display:** Toggle visibility of configuration details, output data, and step execution info for all or current steps to aid debugging focus.
* **Runtime and Configuration Value Inspection:** Compare original configuration inputs with runtime values to verify if flows generate expected data.
* **Modify Inputs Temporarily:** Change input values on paused steps without altering the flow design, enabling testing of different scenarios in real-time.
* **Subflow Debugging:** Debug subflows in separate tabs, maintaining clear context while stepping into nested flows.

## Practical Use and Benefits

ServiceNow customers can use the Flow Debugger to:

* Identify and fix issues within flows by observing exact runtime behavior step-by-step.
* Experiment with different input values temporarily to see how changes affect flow execution without permanent edits.
* Gain detailed insight into both parent flows and subflows in isolated debug tabs for comprehensive troubleshooting.
* Validate complex flow logic and configurations to ensure flows perform as expected before deploying to production.

Overall, the Flow Debugger enhances flow reliability, reduces debugging time, and improves confidence in flow configurations by providing thorough, interactive flow execution control and inspection capabilities.  
Debug flows and subflows from a dedicated Workflow Studio tab. Set breakpoints and step through a paused flow to review configuration and runtime values.  
The flow debugger enables you to perform these actions.

* Debug a flow or subflow from a dedicated Workflow Studio tab
* Set and remove breakpoints.
* Pause a flow or subflow at a breakpoint.
* Review the configuration and runtime values of each step of a flow or subflow.
* Modify the configuration of step input values.
* View the execution details generated by modified input values.
* Step through a flow or subflow line-by-line.
* Step into and out of subflows.
* Step over the next breakpoint.
* Skip over all remaining breakpoints.
* Resume running a paused flow or subflow.
{#flow-debugger__ul_yvx_z1c_hdc}

## Access Debug mode {#flow-debugger__section_uns_psj_mfc}

To debug a flow, open the flow from the Workflow Studio home page and select TestDebug.

## Debug interface and components {#flow-debugger__section_yhg_bfc_hdc}

A Workflow Studio debug mode tab displays flow execution details in a debugging view.  
Figure 1. Sample flow debug tab  
A Workflow Studio debugging view tab consists of these elements.

1. Debug mode label
:   Indicates that you're debugging the current flow or subflow.

2. Debug controls
:   Select a debug control to step through a flow or subflow line-by-line.

    * Resume a flow or subflow to run it until the next breakpoint.
    * Step over a breakpoint to run the flow or subflow without pausing at the next breakpoint.
    * Step into a subflow to debug the subflow in a separate tab.
    * Step out of subflow to return to the debug tab of the parent flow.
    * Skip all breakpoints to resume running the flow or subflow without pausing at any breakpoints.
    {#flow-debugger__ul_m2m_wjc_hdc}

3. Show Action Details
:   Option to show or hide the configuration details, output data, and steps run information for all flow steps. Turn on this option to show action details for all flow steps. Turn off this option to only show action details for
    the current flow step.

4. Debugging state
:   Indicates which step of the flow or subflow you're currently debugging.

5. Breakpoints
:   Set a breakpoint to pause the flow at this step. Remove a breakpoint to run the flow without pausing on a step.

6. Modify inputs button
:   Open the Modify Inputs panel to temporarily change an input's configuration value.

7. Runtime and configuration values
: View the runtime and configuration values generated by the current step. Use these values to determine if the flow generates the data you expect it to.  
Figure 2. Sample stepped into subflow debug tab  
When you step into a subflow, Workflow Studio displays a separate tab to debug the subflow.

8. Subflow debug tab
:   Step into a subflow to debug it in a separate browser tab.

## Modify input values {#flow-debugger__section_zbd_q2w_kkc}

Override the configured value of a paused step to determine how the flow behaves with a new value. Modifying configuration values allows you to test the flow without editing it. You can determine which configuration values enable
the flow to run, and which configuration values produce unexpected or undesired results.  
Figure 3. Sample input modification

You can only modify the value of the current step that the debugger has paused on. Enter a new value and save your changes.

1. Modify Inputs button
:   The Modify Inputs button is unavailable when the Modify Inputs panel is already open.

2. Input that you want to modify
:   Enter or select a new value for the input.

3. Original value
:   See the original configuration values for the inputs.

4. Save modifications
: Save the configuration input values for the current debug session.  
Figure 4. Sample modified values

After you modify a value, use the debug controls to resume the flow to run the step. Look at the step execution details to see both the original configuration value and the modified runtime value.

1. Runtime value for Log action
:   The runtime value of the Log action was changed to be Modified log message.

2. Configuration value for Log action
:   The current configuration value of the Log action remains Original log message.

3. Runtime value for Look Up Records action
:   The runtime value of the Look Up Records action was changed to be 3.

4. Configuration value for Look Up Records action
:   The current configuration value of the Look Up Records action remains 1000.

*[\>]: and then