Execution
Running flows, understanding results, and using iterations.
Running a Flow
Click the Run button in the Action Bar to execute all enabled steps in order. The button changes to Stop during execution, allowing you to abort at any time.
If iterations are configured, the button shows the count (e.g., Run (5x)).
Run Options
Click the dropdown arrow (↓) next to the Run button to open the run options menu. This menu lets you fine-tune how your flow executes.
| Option | Description |
|---|---|
| Run with iterations | Opens a modal to set the iteration count. The flow will run N times sequentially. When active, a badge shows the count (e.g., 5x). |
| Clear iterations | Resets iteration count back to 1. Only visible when iterations are set to more than 1. |
| Parallel execution | Execute steps in parallel where possible. Steps without dependencies run simultaneously. |
| Delay between steps | Opens a modal to set a delay (in milliseconds) between each step execution. Useful for rate-limited APIs. Current delay is shown below the option label. |
| Clear delay | Resets delay back to 0ms. Only visible when a delay is configured. |
| Stop on failure | Checkbox toggle. When enabled, the flow stops immediately when any step fails (request error or assertion failure). When disabled, all steps run regardless of failures. |
Tip: The dropdown is only available when the flow is not running. During execution, only the Stop button is active.
Multiple Iterations
Running a flow with multiple iterations executes the entire flow N times sequentially. Each iteration gets a fresh flow store — extracted variables do not carry over between iterations.
Use Cases:
- •Regression testing: Verify that your API returns consistent results across multiple runs. If iteration 3 suddenly fails while others pass, you've caught an intermittent bug.
- •Performance profiling: Identify response time patterns — the first iteration is often slower due to cold starts (server warm-up, DNS cache, connection pooling). Running 5-10 iterations reveals the true steady-state performance.
- •Stability testing: Check if intermittent failures occur under repeated load. A flow that works once but fails on iteration 7 may point to rate limiting, connection leaks, or resource exhaustion.
- •Load pattern observation: Compare response times across iterations to detect degradation trends — if each iteration gets progressively slower, the server may be under memory pressure.
Tip: Combine iterations with Delay between steps to simulate realistic traffic patterns instead of hammering the API as fast as possible.
Exporting Results
After a flow run completes, the Export button (download icon) in the Action Bar lets you export the execution results. Available formats:
- •Export HTML: A formatted HTML report of the run, suitable for sharing with team members
- •Export PDF: A PDF document of the execution results, ideal for documentation and archiving
- •Export JSON: Raw execution data in JSON format, useful for CI/CD pipelines and programmatic analysis
Note: The Export button is only active after a completed run. It is disabled while the flow is running or when there are no results.