Logs

Click any run — on the project's Runs tab, in Recent runs on the Overview, or from a notification — and the run panel opens on the right. It shows Run #N with its status, the workflow, branch, short commit hash and message, when it started and how long it took, who started it and on which computer, and a Cancel run button while it's running (Run again once it's finished).

Below that, in order:

1. A Setup block — live-only lines from before the first step: which shell and folder a local run uses, or for a server, the connection and the SFTP upload (↑ path/to/file for uploads, ✕ path/to/file for deletions).
2. Each step, collapsible, with its status, the first line of its script, how long it took, and a red exit N badge if it failed. The failing or running step opens automatically.
3. A Collecting artifacts block and the run's artifact list, if it kept any.

Log lines arrive in the open run panel live, pushed from the app's background process as output comes in — not by the UI polling for updates. The panel stays pinned to the newest line unless you scroll up to read. In parallel, the same output is flushed to the API roughly every 500ms and saved against the run, so the log is still there if you close the panel or reopen the run later.

Finding older runs

The project's Runs tab lists every run, newest first, with pages for long histories. Filter by workflow, status, or a date range. The list updates by itself while runs are happening.