When to use it
Use a regular run any time you want a straight-through execution: verifying a new journey works, checking that a recent change didn’t break anything, or producing a result you can share as evidence. For local development, you’ll run this way constantly. For CI, regular runs are the default mode.Key concepts
Sequential execution. Steps run in the order they appear in the journey. Each step’s output — derived values, response data — is available to the steps that follow. Value resolution. Before the run starts, Reqflo resolves all values: run inputs you supplied, the selected Case, Environment values, declared variables, secret references, and any hard-coded values. If required values are missing, the run won’t start — check Run check first. Result collection. Each step produces a result: the request sent, the response received, assertion outcomes, derived values, and any errors or logs. These are collected and displayed in Run mode. Overall outcome. The run passes if all steps pass all their assertions and no unhandled errors occur. A single failed assertion or step error marks the run as failed.How it works
Open Run check
In the editor, open the Run check panel to confirm there are no errors blocking the run. Warnings are worth reviewing but don’t necessarily block execution.
Select a case and environment
Choose the Case that matches the scenario you want to run (for example, “Happy path” or “Missing funding source”). Choose the Environment to target the right system.
Start the run
Click Run. Reqflo compiles the journey and begins executing steps. You can watch results appear step by step.