Test a workflow

Admins can validate their workflow before it runs on live data. Use a test run to simulate a trigger event for a selected user to confirm the workflow logic, conditions, and actions behave as expected. By default, test run uses “Dry Run Mode”, which simulates all actions without producing real side effects.

Step 1: Run a test

Navigate to Apps > Workflow > Workflows.

1. Locate and click the workflow you want to test.
2. Click Test Run at the top right.
   The “Test Run” dialog opens, showing the workflow's trigger and configuration fields.
3. Select the trigger you want to simulate.
4. Fill any additional required fields.
   The fields displayed depend on the trigger type.

Example

• A Manager Changed trigger requires you to select a new manager.
• A Job Title Changed trigger shows a Field Change section where you can specify the old value and new value to simulate.

     5.   (Optional) Leave these fields set to Any value to match any change.

Step 2: Choose the run mode

1. Switch the toggle to control how the test executes.

• Enable Dry Run Mode: Simulates actions without real side effects. For example, no points are awarded, no emails are sent, and no goals are created.
• Disable Dry Run Mode: Executes actions against live data. Use this only when you intend to test with live data.

Step 3: Start the test

1. Click Run Test.
   The dialog shows the test in progress, including the trigger name, run mode (Dry Run or Live), and elapsed time.

     2.   Wait for the test to complete.

Understand test results

After the test completes, the dialog displays the result for each workflow step.

• A green checkmark indicates the step succeeded.
• A red error icon indicates the step failed, with a message describing the issue.

Review the results to confirm that your trigger executed correctly, conditions evaluated as expected, and actions executed in the right order.

After the test

If the results are satisfactory, close the “Test Run” dialog and click Publish to activate the workflow.

If the test reveals issues, edit the workflow, make the required changes, and run the test again before publishing.