Skip to main content
reqflo run <journey> is the core CLI command. It compiles your journey into a build artifact and executes it — locally by default, or in the Cloud Runner when you pass --cloud. All other flags (environment, case, values, data, reporting) compose on top of this base command.

​
When to use it

Any time you want to run a journey outside the web editor: manual verification in a terminal, automated checks in a CI pipeline, or triggered runs from a script.

​
Key concepts

Local execution (default). The CLI runs the journey on your machine using your local environment. Secrets must be available locally; cloud-managed secrets are not accessible without --cloud. Cloud execution (--cloud). The CLI sends the build artifact to the Cloud Runner, which executes it with durable worker execution and cloud-managed secrets. Requires authentication — see Authenticate. Journey identifier. You identify the journey by name or ID. Use the exact name as it appears in Reqflo, or copy the ID from the journey’s Details panel or the CLI mode tab. Build artifacts. Before execution, the journey is compiled into a build artifact. The artifact captures the resolved journey structure, steps, value references, and assertions. This is what actually runs — it makes results repeatable and debuggable.

​
How it works

  1. reqflo run <journey> resolves the journey by name or ID.
  2. The journey is compiled into a build artifact.
  3. The artifact is executed locally (default) or dispatched to the Cloud Runner (--cloud).
  4. Step results, assertions, and any errors stream to stdout as execution progresses.
  5. The command exits with code 0 on pass, non-zero on failure — useful for CI gating.

​
Examples

Run locally: 
reqflo run my-journey
Run in the Cloud Runner: 
reqflo run my-journey --cloud
Run by journey ID instead of name: 
reqflo run jrn_abc123
Run locally and write output to a file: 
reqflo run my-journey --output ./results/run.json
Combine flags — environment, case, and cloud: 
reqflo run my-journey --env staging --case "Happy path" --cloud
The CLI exits with a non-zero status code when any step fails or an assertion doesn’t pass. This makes it easy to fail a CI build gate without extra scripting.