When to use it
| Where you run | Best for |
|---|---|
| Run mode (editor) | Iterating while you build, spot-checking a flow, watching step-by-step results |
| Runbook | Support agents and operational users following a guided, structured walkthrough |
| CLI (local) | Local testing, pre-push checks, scripting |
| CLI + Cloud Runner | CI pipelines, scheduled automation, parallel data-driven runs |
Key concepts
Run mode is the in-editor execution experience. You trigger a run, the journey executes step by step, and results appear alongside each step — request and response details, assertion outcomes, derived values, errors, and logs. Debug mode is a variant of Run mode where the journey pauses at individual steps so you can inspect state before continuing. It’s useful for reaching a specific workflow state and examining what happened. Build artifacts are what actually run. Before execution, Reqflo compiles a journey — its steps, value references, assertions, and execution plan — into a build artifact. Both local and cloud runs work from an artifact; cloud runs store it for repeatability and auditability. See Run artifacts. Cloud Runner executes artifacts with durable worker execution. Runs are tracked, retried on failure if configured, and produce structured output. Use it for anything beyond quick local checks. Data-driven runs supply a JSON or CSV file to drive multiple parallel runs — one per row or record — each producing independent results.How it works
Configure values and pick a case
Before running, confirm that required values are set. Use the Run check panel to catch blockers early. Select a Case to autofill a known value configuration, or supply values directly.
Choose an environment
Pick the Environment that targets the right system — sandbox, staging, or production. The environment provides base URLs and service-level config.
Trigger the run
Click Run in the editor for an in-editor run, or run
reqflo run <journey> from the CLI for a local run. Add --cloud to route execution through the Cloud Runner.Sub-pages
Run mode
Per-step results, assertions, derived values, and evidence in the editor.
Regular runs
A standard run from start to finish.
Debug mode
Pause at steps, inspect state, and optionally abandon the run.
Parallel data runs
Drive many runs in parallel from a JSON or CSV file.
Retries and flaky tests
Retry behavior for unreliable steps.
Local runs
Run journeys locally with the CLI.
Cloud Runner
Durable, trackable cloud execution for CI and automation.
Durable execution
The mental model behind cloud run durability.