Skip to main content
Run mode executes a Journey directly in the Reqflo editor and gives you live, per-step visibility into what happened — not just pass or fail, but the full picture: what was sent, what came back, which assertions held, and what values were produced along the way.

​
When to use it

Run mode is the right choice when you’re building or debugging a journey in the editor and want immediate feedback. It’s also useful for manual verification — running a journey once to confirm behavior before committing a change or handing off to CI.

​
Key concepts

Per-step results. Each step in the journey displays its own result panel after the run. You can inspect the request that was sent (headers, body, URL), the response that came back (status code, headers, body), assertion outcomes, derived values extracted from the response, and any errors or logs produced during execution. Aggregated result. After all steps complete, the run produces an overall result — pass if every step’s assertions passed, fail if any step produced an error or failed an assertion. The summary makes it easy to see at a glance whether the whole Journey succeeded. Evidence. Run results function as evidence of Journey behavior at a point in time. The request/response payloads, assertion outcomes, and logs are all captured and available for review or sharing. Regular vs debug runs. A regular run executes all steps sequentially and collects results. Debug mode adds the ability to pause at any step before it executes, inspect current state, and decide whether to continue or abandon the run.

​
How it works

When you click Run, Reqflo compiles the current journey into a build artifact and executes it. Steps run in order. For each step:
  1. The request is constructed from the step’s request template, with values resolved from run inputs, variables, derived values, environment values, and secret references.
  2. The HTTP request is sent.
  3. The response is captured and assertions are evaluated.
  4. Any derived values defined on the step are extracted from the response and made available to subsequent steps.
  5. Errors and logs are collected.
Once all steps complete, the run is marked as passed or failed and the full result set is displayed.

​
Examples

Triggering a run in the editor Select a Case and Environment, then click Run. Results appear inline next to each step as they complete. Reviewing a failed assertion If a step’s assertion fails, the step result shows which assertion failed, the expected value, and the actual value from the response. Expand the response body to inspect the full payload. Checking derived values After a step runs, expand its result to see the derived values that were extracted. These are the values that downstream steps will use, so confirming them here is a fast way to debug a value chain.