Submit a case from the builder

Submit case in the toolbar runs the flow on a payload you write. It is disabled while the canvas has unsaved edits: save first so the run exercises what you see. Submitting needs cases:write, which the engineer template includes.

​

Choose the version

Run against lists the candidate versions with their roles (active, draft). If the canvas has edits that are not in any saved version, an amber note says so.

​

Edit the payload

The JSON editor is prefilled from the Input node’s schema. The payload must be a JSON object and must match the schema, or the submission is rejected.

​

Dry run vs real execution

By default the run is a dry run: the workflow executes on the engine with side effects suppressed (no provider calls, no information request sent) and the execution is flagged as a dry run. Tick Execute for real (non-dry-run) to create a live case that reaches the queue and your webhooks. The note under the checkbox explains how pinned mock values behave in your environment.

​

Submit and follow the case

The toast shows Dry-run submitted or Real case submitted with a Submitted: link carrying the new case id into the Decision Console. Reset to template restores the schema-derived payload.

​

Replay a past run

From Execution history, Replay opens this dialog prefilled with that run’s payload, against the version open in the builder.