# Run Detail (/docs/executions/run-detail)

Inspect node-by-node execution results and outputs.



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 [#on-the-executions-page]

The standalone Executions page opens a detail sheet for the selected run. It includes:

* Workflow name
* Run status and timing
* Node runs with node type, status, duration, output, and errors
* Copy output or failure details for debugging

In the workflow editor [#in-the-workflow-editor]

The editor executions panel includes the same node-run inspection plus workflow-editor context:

* Live canvas status overlays for the selected execution
* Source badge, automatic run label, optional user note, and AI token/cost totals when available
* 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

Node status indicators [#node-status-indicators]

Each node in the graph or node run list shows its execution status:

| Indicator   | Meaning                         |
| ----------- | ------------------------------- |
| Green check | Success                         |
| Red X       | Failed                          |
| Spinner     | Currently running or waiting    |
| Gray        | Queued, skipped, or not reached |

Inspecting a node [#inspecting-a-node]

Click a node run from the list to inspect:

* **Node type** - which node ran
* **Output** - the data produced by this node
* **Error** - error message and hint (if failed)
* **Duration** - how long the node took
* **Copy output** - copy JSON output or failure details for debugging

Run notes and labels [#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 [#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 [#next-steps]

* [Error Handling](/docs/executions/errors) - common error patterns
* [Running a Workflow](/docs/editor/running) - triggering and inspecting new runs
* [Execution History](/docs/executions/history) - historical run list