Skip to main content
The builder tests a flow with Submit case and shows the result in Executions. Step-by-step: Submit a case from the builder and Execution history.

​
Dry run

The default. The engine runs the graph with side effects suppressed: no provider calls, no information request sent, no webhook to your systems. The execution is flagged as a dry run and filtered under Dry runs in Execution history.

​
Real run

Tick Execute for real (non-dry-run) to create a live case. It reaches the review queue and your webhooks like any submitted case. The note under the checkbox explains how pinned mock values behave in your environment.

​
Inspect a run

Every step shows Result, Changed and Evidence (the complete output and the state the step saw), plus the definition, run payload, dispatch state and raw record.

​
Replay

Replay on a run reopens Submit case with that run’s payload, against the version open in the builder, so a fix can be verified on the exact input that failed.