Run detail
The runs rail, the run head with its status pill and actions, and the Summary, Outputs, Steps, Activity and Integrations tabs of a single run.
A run page tells you what one execution of the pipeline did: which version ran, who started it, what it fetched, the rows it produced, where each step got to, and what went wrong if anything did. Runs open inside the pipeline page (Runs tab), so the pipeline’s hero stays at the top and the runs rail sits on the left.
Open a run from the Runs tab (newest first), from a card’s View Runs, from last ran in the hero, or from the Latest runs page.
- Summarywhat happened, in a sentence
- Outputsthe rows, per output
- Stepsthe diagram, live
- Activityevery fetch and delivery
- Integrationswhat started it, alerts, deliveries
The runs rail
| Element | What it shows |
|---|---|
| Filter runs… | Filters the rail by title or by the parameter values shown inline. No runs match. when nothing does. |
| Groups | Active (queued, running, stopping), then Today, Yesterday, and one group per earlier date. |
| Row | A status icon, the run title (Live run #8 — Sep 15, 06:00), and a meta line: a ticking clock while live; afterwards 48,102 rows · 2m 14s · by timer. by names a person, timer (the schedule) or webhook. |
| Left edge | Coloured by kind: emerald for live, blue for resumed, violet for test, slate for debug. |
Use the ↑ and ↓ keys to move to the newer or older run. Steps and Activity stay selected as you move; any other tab, an open output or a selected step is dropped because the next run may not have it, and the next run opens on its default tab. The keys are ignored while you are typing in a field.
The rail collapses and resizes like the other rails; collapsed rows show their title and meta as a tooltip.
The run head
The head carries the run title with a status pill, a detail line under it, and the actions on the right. Its background follows the state: green for completed, red for failed, slate for cancelled, orange for queued, amber for a run that looks stuck, and the brand colour while active.
| Pill | Meaning |
|---|---|
| Queued | Waiting for an available runner. This run will start automatically. |
| Running / Running — extract_offers | Executing; the current step is named when known. |
| Stopping… | Winding down — the run is being stopped and will finish shortly. |
| Looks stuck | An active run with no activity for 30 minutes: No activity for 34 minutes during extract_offers. You can stop the run, or ask Jason to investigate. |
| Completed | Finished and, for live runs, published. |
| Failed | Stopped on an error. The Summary names the step it failed in; select that step in Steps to read the error. |
| Cancelled | Stopped before finishing, with the reason on the detail line: Stopped by Maya Okafor., Stopped by a user., The worker processing this run was lost., Stopped by the stall watchdog., Stopped after hitting its time limit., or Stopped externally. A reason may follow after a dash. |
Actions
| Action | When | What it does |
|---|---|---|
| Notify bell | While the run is active, in browsers that support push notifications | Notify me when this finishes: sends a browser notification when the run finishes or is stopped. The toast reads I’ll notify you when this finishes — you can close the tab. Click again (Stop notifying me when this finishes) to stop. If notifications are blocked for the site the bell says so: Notifications are blocked for this site. Enable them in your browser settings to be pinged when this finishes. |
| Export | When an output with rows is open on Outputs | Downloads that output as JSON, or CSV for a CSV output. |
| Stop | Active runs | Asks the workers to stop. The run passes through Stopping… to Cancelled; the button stays visible but disabled meanwhile. |
| Resume | Failed or cancelled runs that completed at least one stage | Opens Resume run? and starts a new Resumed run from that stage. It is the main button on a cancelled run and sits beside Fix with Jason on a failed one. See Run lifecycle. |
| Fix with Jason | Failed runs | Opens a new chat scoped to this pipeline with the run, its error and its id, asking Jason to diagnose the problem, repair the pipeline if needed, then re-run it with the failed run’s settings and check the problem is gone. |
| Ask Jason | Runs that look stuck | The same, for a run with no activity for 30 minutes. |
| Delete run | Finished runs, in the menu on the arrow beside the last action (a red button of its own when there is no other action) | Removes the run with its activity, fetched pages and outputs. Datasets it published are untouched. There is no confirmation step; you land on the neighbouring run. |
Summary
The Summary opens with a sentence:
Live run #8 started by the schedule on Sep 15, 2026 against v2 (full input). It completed in 2m 14s, fetching 312 pages and collecting 48,102 rows across 1 output, and published Live product offers v9.
A failed run’s sentence ends It failed after 41s in extract_offers, having fetched 12 pages and collected 0 rows; 2 of 6 steps completed. Click Steps in the facts below to open the diagram, then select the failed step: its Details panel shows the error. A cancelled run says when and why it was stopped; a queued one It is queued and will start as soon as a runner is free.; a running one where it is, how many steps are done and how long is left (~4m left).
Configuration
| Fact | What it shows |
|---|---|
| Kind | The run kind pill. |
| Status | The status pill. |
| Version | v2, linking to that version in the changelog. |
| Started by | A person, the schedule or a webhook. Shown when known. |
| Started, Finished, Duration | Timestamps; Elapsed and Time left while running. |
| Rows collected, Pages fetched | Totals for the run. |
| Steps | 6 of 6 completed, or 2 of 6 completed · failed in extract_offers. Click it to open Steps. |
| Scope | Full input or Cap 1,000 inputs; through <step> when the run stopped at a chosen step; cache-only mode or warm-cache mode when set. |
| Publication | Private · does not publish on test and debug runs. |
| Recovery | On resumed runs: Reused stage extract_offers from source run, linking to the run it reused. |
Inputs and Outputs
Inputs lists each dataset input as Product catalogue v7 · 1,240 rows (a link) and each parameter whose value differed from its default as Region: GB (default US). Outputs lists Datasets: Live product offers (v9), deliverable cards, and one card per output: a dataset card when published, or offers · 118 rows · not published for a test, debug or stopped run, which opens the run’s own copy of the rows.
Outputs
Outputs shows the rows the run produced, one worksheet tab per output when there are several (Deliverables 2, offers 48,102, matches waiting with a spinner for one still being written). A single output shows the banner Added to dataset Live product offers as v9 · 48,102 rows with View dataset.
The table is the run’s rows. Click a row to open Row details:
Previous row (←), Next row (→), Open in full page and Close (Esc) sit in the header.
When there are no rows to show, the tab says why:
| Run | Message |
|---|---|
| Queued | Results will appear after the run starts. |
| Running or stopping | Results will appear when they are ready. |
| Failed | This run failed before producing results. |
| Cancelled | This run was stopped before producing results. |
| Completed | This run completed without producing results. |
The Deliverables tab lists Files this pipeline built on this run.; each card’s menu has Preview & history, Download and Delete series (Delete every version of "<name>"?).
Steps
Steps is the pipeline diagram with this run’s facts on it: row counts on the edges, a pulse on the step that is running, and a camera that follows the active step while the run is live. Selecting a block opens it in the panel on the right; Escape or × returns to follow mode.
| Panel tab | What it shows |
|---|---|
| Details | The same reading panel as the pipeline’s diagram (what the step reads, saves and which rules apply), plus this run’s facts for it: status, rows in and out, pages fetched, elapsed time, and the error when the step failed. Open output or Open dataset go onwards. |
| Data / Data (1,240) / Input Data | The rows the step produced: Partial preview while it is running, Intermediate output afterwards, Reused exact dataset revision for a reused stage. Messages: This stage is waiting to start., No rows produced yet., This stage produced no rows. |
| Pages (12) | The pages the step fetched, when it fetched any, each with its outcome (ok, blocked, fail, running, cached). |
Selecting an input block opens Inputs: Input values captured at run start., with Parameters (2) and Pipeline inputs (1), each with its type and value, and an Export button that downloads the exact run configuration so the run can be repeated. Selecting an output pins it and shows its rows. When the run has no diagram to show, the tab says why:
| Run | Message |
|---|---|
| Queued | Waiting to start… |
| Running or stopping | Building the graph… |
| Failed | No steps were recorded before this run failed. |
| Cancelled | No steps were recorded before this run was stopped. |
| Completed | No steps were recorded for this run. |
The stage labels under each step summarise its state: Waiting to start, 340 of 1,240 processed, Failed after 12 rows, 1,240 rows, 1,240 rows · exact revision.
Activity
Activity is the run as a feed of events, newest at the bottom, each stamped with the time since the run started (0:01:42).
| Row type | What it shows |
|---|---|
| Page fetch | Host and path, method, size, duration, and flags such as Reused from cache, Served this page, No rows returned, blocked or failed. Expand it for Result 24 rows, Requests, Downloaded, Duration, and a link to the fetched content. |
| Extraction | Rows extracted from a page; No rows extracted is flagged as a warning. |
| Browser session | A recorded browser session you can open where one was kept; otherwise Browser session unavailable. |
| Delivery | Delivered to Live product offers, or Failed. |
| Lifecycle | Dimmed rows for dispatch, start, each step’s completion, stopping, resuming, finishing and failing. |
While the run is live the feed ends with Watching for the next event… (or Waiting for activity… before the first one). An empty feed on a finished run reads No activity recorded for this run.
Integrations
Integrations shows how this run touched the outside world. The tab is always there; it carries a count once the run has integration activity.
| Section | Help text | Empty, while the run is active | Empty, once it has finished |
|---|---|---|---|
| In | What started this run or pulled data in for it. | Nothing external started or fed this run. | Nothing external started or fed this run. |
| Alerts | Alert rules this run or its data set off, and where each was sent. | Alert rules are checked when the run finishes. | No alert rules fired. |
| Out | Where this run’s rows were sent. | Rows are sent on once the run publishes its data. | This run’s rows weren’t sent anywhere. |
Each In and Out row has a status icon (Succeeded, Failed or Skipped), the integration, what happened, the error in a red box when a delivery failed, and how long ago. Each Alerts row names the rule (a link) and why it fired, where the alert went (Sent to, Not sent to or Couldn’t send to and the integration), and how many matching rows it carried.
A finished run with no integration activity at all reads Connect a service in Integrations to trigger runs, alert people or send rows on. The integrations wired to a pipeline, as opposed to what happened on one run, are on its Integrations page.
The favicon pulses while a run you have open is active, and the page keeps itself current over a live connection with polling as a fallback. Leave the tab open in the background and glance at it.