Runs
Execute QA runs and interpret results.
Run Types
Canary supports three types of runs, each designed for different testing scenarios:
| Run Type | Purpose | Prerequisites |
|---|---|---|
| Test Runs | Execute all published workflows as regression tests | At least one published workflow |
| Chaos Runs | Autonomous AI agents explore and test your app | A property configured |
| Workflow Runs | Execute a single workflow (documented below) | A workflow to run |
Workflow Runs
A workflow run is a single execution of one workflow, capturing pass/fail outcomes, screenshots, and video recordings.
Starting a run
- Open a workflow in the Flow Designer
- Click Run Flow in the header
- The sidebar switches to the Runs tab showing live execution
Runs can also be triggered as part of a smoke suite or via the API.
Run statuses
| Status | Meaning |
|---|---|
| Queued | Waiting to start |
| Running | Execution in progress |
| Waiting | Paused at a Wait node—will resume automatically |
| Success | All steps passed |
| Failed | One or more steps failed |
| Canceled | Manually stopped |
Live execution
While a run is in progress, you'll see:
- Browser stream: Live view of the current browser state
- Agent reasoning: What the AI is doing at each moment
- Canvas status: Running nodes pulse; completed nodes show green (success) or red (failure)
Run details
Click any run to see:
- Video: Full session recording with agent thoughts overlaid on the timeline
- Screenshots: Per-step browser captures
- Steps: Each node's status, duration, and any error messages
Investigating failures
When a run fails:
- A failure banner shows which step failed and the error message
- Click View Details to open the failure drawer with:
- Failure screenshot (browser state at the moment of failure)
- Additional context for debugging
- The failed node is highlighted on the canvas
Wait nodes
Workflows with Wait nodes pause mid-execution:
- Run executes until it hits the Wait node
- Status shows Waiting with a countdown timer
- Execution resumes automatically after the delay
- The next Login node re-establishes the browser session
Artifacts
Each run stores:
| Artifact | Description |
|---|---|
| Screenshots | Browser capture at each step |
| Video | Full session recording |