Skip to main content
Test a saved workflow version on data you choose, then follow every run in the Runs tab: which path it took, what each step received and returned, and why a step failed. Do both before you activate a workflow and whenever it doesn’t do what you expect.
Open a workflow in Agentic Workflows. Test needs Workflows (Write) or Run workflows (Write). The Runs tab needs Workflows (Read); canceling and resuming runs needs Workflows (Write).

Run a test

1

Select a saved version

Pick a version in the version menu next to the workflow name. Test is turned off while the editor shows your draft (This workflow is a draft and cannot be tested), so click Save first. The version doesn’t need to be active.
2

Open Test Workflow

Click Test. The Test Workflow dialog asks for the data the trigger would normally provide. The fields depend on the trigger:
3

Start the run

Click Test. The editor switches to the Runs tab and follows the run step by step as it happens.
A test run executes every step with all its side effects. Replies, emails and WhatsApp templates reach the customer, sessions are tagged, assigned or closed, and HTTP and Slack steps call the real endpoints. Test on a session you own, such as one you opened yourself in the widget.

What’s different about a test run

Classical IVR steps such as Speak Text and Transfer Call need a live call, so they fail in a test run. Test those with a real call to the IVR number.

Read the Runs tab

The Runs tab appears after the first save. It lists the runs of the version on the canvas, newest first. Switch versions to see their runs. Each row shows when the run started, Test for test runs, a short run ID, how it started (Automatic, Manual or Scheduled) and how long it took. Use Search runs… and the filter button to narrow by STATUS or DATE RANGE (Today, 3d, 7d, 30d). Click the refresh icon to load new runs. Open a run to paint it on the canvas: each step gets a status badge, and steps the run never reached stay plain. The run panel shows:
  • The status, how the run started, its duration and the run ID (click to copy). Use the arrows to move to a newer or older run.
  • Failed at, naming the step that failed and its error. Click it to open the step.
  • Steps: every step in the order it ran. Use ↑ and ↓ to move between steps; the canvas follows.
  • Output: what the run returned, when it ends with a step such as Aggregate Workflow Results.
  • Logs: the run’s log, in order.
Click a step to see its Input and Output. The trigger shows its Payload, an If Block shows which branch it took, and a failed step shows This step failed with the error. Right-click a step for Copy input, Copy output, Copy step ID and Edit this step, which takes you back to the editor with that step open.

Run statuses

Steps can also show Skipped.

Cancel or resume a run

  • Cancel run stops a run that is running or waiting. Steps that already ran are not undone.
  • Resume restarts a failed or queued run with the data it originally received. It starts again from the first step, so steps that completed before the failure run a second time. Check what they did (a reply already sent, for example) before you resume.

Common failure states

Get notified about runs

To send run results to your own systems, subscribe to workflow.run.succeeded and workflow.run.failed in Settings → Webhooks. Failure events include the workflow name, the session the run acted on (empty for cron, webhook, form and manual triggers) and the error. See Webhooks setup.

Troubleshooting


Build a workflow

Re-check steps, variables, versions.

Triggers and steps

Trigger data and step requirements.

Workflows overview

Life cycle and permissions.

Webhooks setup

Receive run events.