# Running a Workflow (/docs/editor/running)

How to trigger and inspect executions from the editor.



Click the **Run** button in the top toolbar to execute your workflow.

What happens [#what-happens]

1. An execution record is created (status: pending)
2. The runtime picks it up and starts processing (status: running)
3. Nodes execute in graph order - each lights up as it runs
4. On completion, the execution shows success or failure

During execution [#during-execution]

* Nodes show real-time status: spinner (running), green check (success), red X (error)
* The executions panel shows progress and live node output as rows become available
* Only one execution runs at a time per workflow

Executions panel [#executions-panel]

The editor's executions panel is the fastest way to inspect recent runs without leaving the workflow.

Run list [#run-list]

The top section lists recent executions. Each row includes status, relative time, duration, node counts, source, and automatic labels when Solaris AI Flow can infer them from the trigger context. Runs involving AI nodes may also show a compact cost/token chip.

Use **Load older runs** to page back through history.

Run details [#run-details]

Selecting a run opens node-level details below the run list:

* Overall status, duration, source, and AI cost/token totals when available
* Optional user note. Click **Add note** or an existing note to edit it inline.
* Rerun controls for supported trigger contexts. Webhook reruns use the trigger's sample payload; they do not replay the original webhook delivery.
* A node mini-map for longer runs. Click a segment to select and scroll to that node run.
* **All** / **Failed** filters and node-run search for large workflows
* Node output, errors, timing, and copy/debug details

If a run fails, opening it auto-scrolls to the first failed node when possible.

After execution [#after-execution]

* Select a node run from the executions panel to see its output and errors
* Use the node mini-map, failed filter, or search to find relevant nodes in longer runs
* Open the full **Executions** page for historical filtering across workflows
* Failed nodes show their error message in the panel and on the canvas

Duplicate protection [#duplicate-protection]

If you click Run while a previous execution is still active, it is rejected. Wait for the current run to complete.

Preview and upstream runs [#preview-and-upstream-runs]

Node settings can run upstream samples for previewing Code and Transform nodes. These preview runs count as monthly runs and can execute side-effecting upstream nodes only after confirmation. They are hidden from the normal execution list but included in lifetime usage totals.

Next steps [#next-steps]

* [Execution History](/docs/executions/history) - view all past runs
* [Run Detail](/docs/executions/run-detail) - inspect node-level results
* [Configuring Nodes](/docs/editor/configuring-nodes) - input/output panes and live previews