---
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 flow

# Test a flow {#ariaid-title1}

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

Before activating a flow so other users can access it, test to make certain it works
the way you expect.

## Before you begin

Role required: flow_designer or admin

## About this task

Testing a flow bypasses the flow trigger conditions to run it with the test data you provide. For example, testing a flow with a record Created trigger causes the system to act as if the selected record was created. For a list of data pills available by trigger type, see [Workflow Studio flow trigger types](https://servicenow-prod.fluidtopics.net/Soppqn4o7y_LAxzJX99Zpw "Each trigger type defines when a flow starts and the starting data available to it. There are triggers for record operations, dates, and application operations.​").  
Note:  
Because testing a flow creates or changes records on the instance, flow designers should always test flows on a non-production instance containing relevant demonstration data.

## Procedure

1. Navigate to AllProcess AutomationFlow Designer, then double-click the row for the flow you want to test.
2. Save the flow.
3. Select Test.  
   The system displays the Test flow dialog. The contents of the Test flow dialog depend on the type of trigger.
4. If the flow has a record trigger, create or select a record to use for the test.  
   To create a record, select the Create new record button ![Create new record button]().
5. If the flow has a record Updated or Created or Updated trigger, specify which fields and values changed in the update.  
   To specify a field value change, select the Create new changed field button ![Create new changed field button]() for each field whose value you want to change. Complete the changed field details for each changed field.  
   {#flow-test__table_pqm_4sc_2jb__entry__2}

   | Field | Description |
   |-|-|
   | Field Name | The field updated by the test. |
   | Previous Value | The field value prior to the update. |
   | Current Value | The field value after the update. |
   | Previous Display Value | The field display value prior to the update. |
   | Current Display Value | The field display value after the update. |
   [ ]

   {#flow-test__table_pqm_4sc_2jb}
6. Select Run Test.  
   Note:  
   Select the Run test in background option to test a flow asynchronously in the background.  
   The system tests the flow.
7. Select Your test has finished running. View the flow execution details.  
   Note:  
   This link is created irrespective of your choice for the Run test in background option. If you have selected 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 flow only after execution is completed.  
   The system displays the flow execution details for the test.

## 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.").

*[\>]: and then