Workflow Runs

The editor can execute a saved workflow with test input, stream a live trace, and store a compact run record for later inspection. Testing still executes real actions: review permissions and targets before running a workflow with side effects.

Test Run

Choose Test run in the editor header. The input dialog sets both {{input}} and {{transcription}} to the text you provide.

One-shot run

Choose One-shot, enter representative input, and select Run. Echo executes the workflow normally, opens the console, highlights completed or failed nodes, and marks edges that carried data. The status line reports completion or failure, and the run is added to history.

The graph currently shown in the editor is not implicitly saved by Test run. Use Save before testing changes you want the backend to execute.

Step-by-step

Choose Test run → Step-by-step to pause before each action. The step bar shows the current position and exposes:

• Previous (shown as Prev) to move the inspector cursor to an earlier traced step. It does not undo execution.
• Next to move forward through an already recorded step or, at the live frontier, let the paused action continue.
• Abort to cancel the active step-mode run.

Step mode is a debugger, not a safety sandbox. When you choose Next at the live frontier, the real action can read, write, call, or control whatever its configuration permits. Review Recipe security first.

Console and node I/O

The Console lists each traced action with its status, name, output preview, error, and duration where available. Select a row to open the step inspector:

• Input is the preview captured when the step started or paused.
• Output is the preview captured when it completed.
• Error appears for a failed step.

The UI intentionally stores previews rather than promising a complete audit log. An edge that actually carried data can also be selected to inspect its recorded value; full edge values are capped before they are emitted and persisted.

Run history

Choose History to load stored runs for the current workflow, newest first. Each row shows workflow name, trigger, status, and start time. Clear deletes all stored workflow-run records, not only the current workflow's filtered list.

A stored record contains the run status, step status/output previews/errors/durations, and traversed-edge previews. It is useful for debugging, but it is not a backup of external files, network requests, clipboard state, or the complete runtime environment.

Replay

Select a run in History to replay its trace on the canvas. Replay is read-only: it reconstructs node states and traversed-edge data from the stored record and does not execute the workflow, re-run an action, or reproduce an external side effect.

While replay is active, the editor shows Replaying a past run. Select exit to return to the live trace. If you need to execute the workflow again, leave replay and start a new Test run explicitly.