Run Detail

Run details show a breakdown of a single workflow execution with node statuses, output, errors, timing, and debugging actions.

You can inspect run details from:

• The Executions page by selecting a run
• The workflow editor's Executions panel after a run starts or finishes

On the Executions page

Clicking a run on the Executions page expands it in place into a waterfall, without navigating away or covering the list.

Every node that ran gets a row: its type, a status dot, and a bar drawn at the node's real offset and width inside the run window. That means a node that took 2.9 seconds out of a 3.4-second run has a bar covering most of the track, so the slow step is obvious at a glance rather than something you have to work out from timestamps. Nodes that never finished (skipped, or cut short by a watchdog timeout) show a dash instead of a duration, so they can't be mistaken for still running.

Under each node you'll find:

• Its error, with the remediation hint broken out separately when the executor supplied one
• Its output, collapsed by default so a long run stays scannable. Expand it to read the payload or copy it.
• A notice when the output was truncated, or when a Dataset read returned partial results

Large outputs are stored outside the database and fetched on demand when you expand them, so opening a run with a big payload doesn't slow down the list.

In the workflow editor

The editor executions panel gives you the same node-run inspection, plus the things that only make sense while you're looking at the canvas:

• Live canvas status overlays for the selected execution
• An optional user note you've written on the run
• A node mini-map for longer runs. Click a segment to jump to that node run.
• All and Failed filters
• Node-run search by label, type, or response name
• Automatic scroll to the first failed node when opening a failed run
• Rerun controls for supported terminal runs

Trigger source, the automatic run label, and AI token/cost totals appear on the Executions page too, so you no longer have to open the editor to see them.

Node status indicators

Status uses one colour language across the canvas, the editor panel, and the Executions waterfall:

On the canvas and in the editor panel this reads as a check or X on the node itself. In the Executions waterfall it's a status dot plus the node's timing bar, which is drawn in the same colour.

Inspecting a node

Wherever you're looking at it, a node run tells you:

• Node type - which node ran
• Duration - how long that node took
• Output - the data it produced, copyable as JSON for debugging
• Error - the message, plus a remediation hint when one is available

In the editor panel you click a node run to open it. On the Executions page the waterfall already lists every node: errors show inline, and outputs are one click away.

Run notes and labels

In the workflow editor, Solaris AI Flow can show an automatic label from trigger/run context so repeated runs are easier to recognize. You can also add your own note from the editor executions panel. Notes are saved on the execution record and are meant for debugging context, such as "before changing slippage" or "webhook test payload".

Rerunning

From the editor executions panel, supported terminal runs can expose a rerun control:

• Manual-node runs can run that node again.
• Cron runs can fire the cron trigger now.
• Webhook runs can run with the trigger's configured sample payload.

Webhook reruns do not replay the original webhook delivery payload.

Next steps

• Error Handling - common error patterns
• Running a Workflow - triggering and inspecting new runs
• Execution History - historical run list