Console & Run Monitoring

The bottom console is your window into everything the engine is doing: queued and active runs, live logs, output previews, and run reports.

Queue and history

• Queue: runs that are pending or executing, with per-run status. Cloud runs show their dashboard link.
• History: completed, failed, and cancelled runs. Each entry carries its status and outputs; selecting a run scopes the Logs tab to it.

Run lifecycle states are documented in the Execution Model page.

Logs

The Logs tab streams engine output grouped by run and node. Node ids are resolved to friendly names, entries have severity levels (info/warn/error), and long details expand inline. Clearing the view is local-only, it never deletes run artifacts.

Previews

The Previews tab collects images (PNG/JPG/SVG/…) and HTML files produced by completed runs, plots, MultiQC reports, and anything else your nodes emit, viewable without leaving the app. Previews are read from on-disk run artifacts, so this tab is available on desktop (or a self-hosted server), not in the cloud editor.

Report

The Report tab renders the per-run HTML report generated from on-disk run artifacts (/api/runs/:id/report), including provenance details: which nodes ran, with what parameters and tool versions. Like Previews, this tab is desktop/self-hosted only.

Errors and recovery

Failures surface in the queue/history entry and in the log stream at error level, tagged by node. From there you can:

• fix the node’s parameters and re-run, completed upstream nodes are reused via checkpoints;
• cancel a running job;
• resume a cloud run that was interrupted (for example by a spot instance reclaim) from its dashboard.

Cloud differences

In the cloud editor, the console shows the same queue, history, and log stream, backed by the cloud run API. The Previews and Report tabs are hidden there (they read the local filesystem); use the run’s dashboard link to inspect cloud run artifacts instead.