Skip to main content
The Cloud Runner is Reqflo’s cloud execution environment. When a journey runs in the cloud, it first compiles into a build artifact and then the Cloud Runner executes that artifact with durable worker execution — meaning runs are resilient to transient failures and produce reliable, auditable results. Runner configuration in Admin controls how that execution environment is set up for your workspace.

​
When to use it

Configure runners in Admin → Runners when:
  • You’re setting up cloud execution for the first time.
  • You need to update runner credentials or connection settings.
  • You want to adjust execution parameters like timeouts or concurrency.
  • You are troubleshooting a cloud run that isn’t executing as expected.

​
Key concepts

Build artifacts. Before a journey can run in the cloud, it is compiled into a build artifact. The artifact captures the journey structure, steps, value references, assertions, and execution plan in a form the Cloud Runner can execute repeatably. See Journeys: versioning and artifacts for more on how artifacts are created. Durable execution. The Cloud Runner uses durable worker execution — if a transient failure occurs mid-run, execution can resume rather than starting from scratch. This makes cloud runs appropriate for longer workflows and production-grade validation. Local vs. cloud runs. Running a journey with reqflo run <journey> defaults to local execution. Adding --cloud sends it to the Cloud Runner. The runner configuration here governs all --cloud runs from the CLI and all runs triggered directly from the Reqflo editor in cloud mode. Secrets in cloud runs. When the Cloud Runner executes a journey, it resolves secret references using the workspace’s cloud-managed secret store. Make sure any secrets referenced by the journey are registered in Admin: secrets management before running in the cloud.

​
How it works

1

Open Admin → Runners

You’ll see the current runner configuration for the workspace, including connection status and any active runner instances.
2

Configure runner settings

Set the parameters your organization requires — connection credentials, execution region, timeout settings, and concurrency limits. The exact options depend on your workspace’s runner setup.
3

Verify the connection

Use the connection check to confirm the Cloud Runner is reachable and configured correctly before sending live runs.
4

Run a journey in the cloud

From the editor, select cloud execution mode, or use the CLI with the --cloud flag.

​
Examples

Running a journey in the cloud from the CLI. 
reqflo run checkout-flow --env staging --case happy-path --cloud
Triggering a cloud run in CI. 
reqflo run checkout-flow \
  --env production \
  --case smoke-test \
  --cloud \
  --reporter junit \
  --output results/checkout-results.xml
Running a data-driven cloud run. 
reqflo run checkout-flow \
  --env staging \
  --data test-cases.csv \
  --cloud \
  --reporter json \
  --output results/