Managing Workflow Runs

When a workflow action inside a Process Flow fails, gets stuck, or needs to be re-run after a fix, the platform gives you controls directly on the Process view card — and in the Logs view for standalone runs.

Viewing a failed run

When a workflow action reaches a terminal failed state, the action card in the Process view shows:

• An inline failure summary — the output.reason string and any per-block errors collected from the run's trace spans.
• An "Open full run" button (canvas-backed actions only), located in the card's Workflow section, that opens a side panel showing the full block-level trace, per-block error messages, and timing — without leaving the Process view.

The "Open full run" button is only shown for canvas-backed actions (system-agent steps @system/… have no canvas run to open). Opening the panel requires only read access.

Cancelling a stuck run

A workflow action that is executing — including one parked on a Human-in-the-Loop (HITL) approval gate — shows a "Cancel run" button on the action card. Clicking it opens a confirmation dialog; confirming sends a cancel request to the server.

What happens on cancel:

1. The platform stops the running workflow immediately, including any approval gate it is parked on — a HITL-parked run is fully stopped, not left in limbo.
2. The run is recorded as cancelled in the Logs view; the run and its approval gate are cleaned up.
3. The workflow action on the Process card is marked failed with output.reason = "Cancelled by <user>". This is the terminal state that also enables the Rerun button.

The "Cancel run" button is visible only while the action is in_progress. It is not shown for completed or already-failed actions.

The Logs view cancel is also fixed. Prior to this release, cancelling from the Logs view did not fully stop an in-progress run; it now behaves identically to cancelling from the Process view.

Rerunning a workflow action (Process view — in-place)

When a workflow action is in a terminal state (failed, completed, or skipped), the action card's Workflow section shows a "Rerun" button. Clicking it re-dispatches the action in place against the same Process Flow instance:

• The previous output, content, and execution id are cleared.
• The action status resets to pending.
• The platform re-dispatches the action through the same path used for automatic stage-entry dispatch, so all the same grounding, retrieval, and output-surface logic runs again.

This is the right choice when the workflow failed due to a transient issue (missing integration config, a flaky external call) or when you have fixed the root cause and want to re-run without starting the whole process over.

Rerunning a workflow run (Logs view — fresh run)

In the Logs view, a terminal run shows a "Rerun" button in the run-detail sheet header. This creates a fresh standalone run using the prior execution's stored input:

• A new execution id is minted.
• The run is scheduled as a fresh instance with the same input data from the original run.
• The new run appears as a separate row in the Logs view and can be inspected independently.

This is distinct from the Process-view rerun: it creates a new top-level run unattached to the process action's state. Use it when you want to re-execute the workflow standalone for diagnostic or testing purposes, or when the original run was started from the Logs view rather than a process action.

Which rerun to use

Reading a Document action's output

document actions let you write or Generate with AI (then Regenerate) the document body. The content is authored in Markdown, but you rarely want to read it as raw Markdown — headings, lists, and tables are hard to scan, and pasting the source into a tool that doesn't understand Markdown (e.g. Outlook) carries the #, *, and | characters across.

Each Document action card therefore has an Edit / Preview toggle:

• Preview (the default whenever the action already has content) renders the Markdown into a clean, styled document — the same renderer used for AI agent output. This is the view to read from and to copy-paste rich text into email or a document editor.
• Edit shows the raw Markdown textarea for authoring or tweaking the body.

Clicking Generate with AI or Regenerate switches to Preview automatically once the result is ready, so you see the finished document styled rather than as Markdown source. An empty action opens in Edit so you can start writing straight away.

Downloading output as PDF

When a workflow action completes with a text output, a "Download as PDF" button appears in the action card's Output section. Clicking it opens your browser's native print dialog pre-set to the output content — choose "Save as PDF" as the destination to export the result.

The same button appears on a Document action's Preview (see above) and in the "View Output" sheet (opened via the "View output" button) for actions that write their result to the instance knowledge base.

Tips:

• In Chrome and Edge, select "Save as PDF" from the Destination dropdown in the print dialog.
• In Firefox, choose "Microsoft Print to PDF" or "Save to PDF" from the printer list.
• In Safari on macOS, click the PDF dropdown in the bottom-left of the print dialog and select "Save as PDF".
• The exported PDF includes only the output content — the surrounding process UI and navigation are hidden automatically.

Related