---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Test a subflow

# Test a subflow {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can test a subflow alone, or when added to a flow. When testing a subflow alone, you must define the inputs that the subflow uses in its actions. Because a subflow does not have a trigger, testing a subflow runs the actions using the defined input values. Unless updated, subsequent tests use the same inputs defined in the initial test run.

## Before you begin

[Create a subflow in Workflow Studio](https://servicenow-prod.fluidtopics.net/7jAqeN4sVKi_m~WDCkNaFQ "Reuse an entire flow's content as a subflow. Define the input data the subflow uses and the output data it generates. Call subflows from other flows or script.​") that contains at least one action and save it. Workflow Studio only tests saved subflows that contain at least one action.

Role required: flow_designer or admin

## About this task

Because testing a subflow creates or changes records on the instance, flow designers should always test subflows on a non-production instance containing relevant demonstration data.

## Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Click the subflows tab and open a saved subflow.
3. Click Test.  
   The Test Subflow dialog opens.
4. Define input values for the subflow to use in its actions.  
   The values defined are remembered on future test runs.
5. Click Run Test.  
   Note:  
   Select the Run test in background option to test a subflow asynchronously in the background.

   If you select the
   Run test in background option, the execution
   details are displayed only after the execution is completed
   asynchronously in the background. Also, the execution details are
   associated with the subflow only after execution is
   completed.
6. After the flow executes, click Subflow has been executed. To view the subflow, click here.  
   The Execution Details open.

## What to do next

Review the [Flow execution details](https://servicenow-prod.fluidtopics.net/74QTppHjnADqEx74Gqai7w "View run-time information about an action or flow directly from the design environment, such as the current state, items run, and values produced. Open related records from embedded ServiceNow AI Platform editors or in a new tab.").

Once the subflow behaves as desired, you can [publish the subflow](https://servicenow-prod.fluidtopics.net/GFVD24V8Gmq2mQOp53GZ9A "Publish a subflow to make it available to other users and to add it to activated flows.") and add it to a flow.

*[\>]: and then