The pipeline page

A pipeline is the repeatable definition of a dataset. Jason builds it, workers run it, and the pipeline page is where you read what it does, run it, and ask for changes. This page covers the list of pipelines, the cards that summarise each one, and the pipeline page from the hero down to its four sections.

1. Pipelines listevery pipeline and dataset
2. Pipeline pagehero, sections, rail
3. RunRun Pipeline or a schedule
4. Outputsdatasets, files, dashboards

The Pipelines list

Open Pipelines in the left navigation. The list holds everything in the workspace that produces or holds data: every pipeline with its output datasets, plus standalone datasets that nothing produces (uploads, imports, samples).

Toolbar

Option	Values	Default	What it does
Search	Free text, placeholder Search pipelines and datasets…	Empty	Matches a pipeline’s name, description or slug, or the name of any dataset it publishes. Standalone datasets match by name. While you search, folders are flattened so matches from every folder appear.
Status	Everything · Active Revision · Active runs · No Active Revision · Failed · Uploaded data	Everything	Filters the list. Each option shows its count. Active Revision means a reviewed version is live; No Active Revision means the build has not finished; Active runs means a run is queued, running or stopping; Failed means the last run failed; Uploaded data shows only standalone datasets.
Sort	Last Updated · Date Created · Name	Last Updated	Orders the cards.
Clear filters	Button	Hidden	Appears when a search or filter is active and resets both.
View options	Large grid · Small grid · List	Large grid	Changes the layout. Your choice is remembered per page in this browser.
New Pipeline	Button with a menu	—	Opens the new-pipeline composer. The menu also offers Upload data, Open playground and New folder.
Pagination	25 · 50 · 100 per page	50	Shown only when there are more items than the smallest page size.

Sections and folders

Items sit in two collapsible sections inside the panel: Pipelines and Other datasets, each with a count. When the current folder has subfolders or a parent, a Folders section appears above them.

• Folder tiles show the folder name, <n> subfolders · <n> items, and a few item icons. The tile menu offers Rename folder and Delete folder. Inside a folder, a Back to tile returns to the parent.
• Drag to move. Drag one or more selected cards onto a folder tile to move them. Or select cards and use Move to folder in the bulk action bar, which opens a folder picker with an inline New folder field.
• Lasso select. Drag on empty panel space to draw a selection rectangle around several cards.

The New Pipeline composer

New Pipeline opens a dialog titled New pipeline where you describe what to collect. Everything you type becomes the opening message of a new chat with Jason.

Option	Values	Default	What it does
Brief	Multi-line text, placeholder Describe what you want to collect. Type @ to reference a dataset, or attach files.	Empty	What you want. Drop files onto the box to attach them.
@ mentions	Type @ and a word	—	Opens a Datasets picker of ready datasets. Arrow keys move, Enter or Tab inserts the reference, Escape closes.
Attach	File picker (CSV, PDF, image and more)	None	Attached files show as removable chips. Jason reads them as part of the brief.
Link dataset	Checklist of ready datasets in this workspace	None	Links datasets without mentioning them in the text. Linked datasets show as chips you can unlink.
Suggestions	Pills	—	Ideas based on your workspace. Click one to fill the brief.
Start building	Button, also ⌘↵ / Ctrl+Enter	Disabled until the brief has text	Starts a new chat with Jason and opens it.

I want to build a pipeline: track the price and promotion of every product in @product_catalogue across Amazon, Argos and Currys. One row per product per retailer per day. Refresh every morning.

The build itself happens in the chat. See Chatting with Jason and Your first pipeline.

Pipeline cards

Each pipeline is a card. The card shows the pipeline icon, a clock and the cadence when it is scheduled, the name, its output counts (for example 1,274,880 rows), a status line, and a timestamp: a live clock while the last run is running, otherwise how long ago it ran. Next run appears under the status when a schedule is set.

The status line and the card colour follow the pipeline’s health:

Card colour	Status text	When
White	Not run yet	The pipeline has never run.
White	Building / Blocked	The first version is still being built, or the build is waiting on something.
Blue	Queued / Running / Stopping	A run is in flight. Updating shows while Jason is changing the pipeline.
Emerald	Finished successfully	The last run completed and published.
Brand purple	Repaired	The last publish came from a version that an automatic repair produced after the previous failure.
Amber	Awaiting publication, No recent successful run, Last run cancelled, Needs attention	Something to look at: the run has finished but has not published yet, a scheduled pipeline has missed two slots, or the last run was stopped.
Red	Needs attention	The last run failed.

The same cards appear on the Home page in the Pipelines section (up to six, running pipelines first, then Show N more pipelines), and pipelines that failed or need attention also appear in Home’s Needs attention list with the failure time and reason.

Hover a card for its checkbox and its Actions menu:

• Run. Starts a run with the pipeline’s default settings and opens the run page. Shown only when the pipeline has an active version.
• View Runs. Opens the pipeline’s newest run.
• Change workspace. Copies or moves the pipeline to another workspace (below).
• Delete. Asks you to confirm, then deletes the pipeline. Its datasets stay.

In List view the same information is laid out in columns: icon, name, counts, cadence or On demand with the next run, then status and time.

Bulk actions

Select cards with their checkboxes, the lasso, or (select all) in the subtitle. The bulk bar shows <n> selected with:

• Run. Runs every selected pipeline that has an active version, each with its defaults. Datasets and unbuilt pipelines are skipped.
• Copy. Opens Change workspace for the selected pipelines.
• Delete. Confirms Delete <n> item(s)? This cannot be undone., then deletes the selected pipelines and standalone datasets.
• Move to folder. Moves the selection into a folder.

Runs started from a card or the bulk bar use the pipeline’s default settings. To pick a dataset revision, change a parameter or set an item limit, open the pipeline and use Run Pipeline. See Running a pipeline.

Change workspace

Change workspace copies or moves pipelines between workspaces you can access.

Option	Values	Default	What it does
Change method	Copy (keep the original) · Move (remove the original)	Copy	Whether the source workspace keeps the pipeline.
Destination workspace	Workspaces grouped by organisation	None	Where the pipelines go. Members of that organisation will be able to see them.
Dataset history	Structure (no rows) · Current (active rows) · All versions (full history)	Current	How much of each linked dataset travels with the pipeline.
Pipeline version history	Checkbox	Off	Include earlier versions and their changelog entries.
Completed run history	Checkbox	Off	Include past runs with their outputs, logs, fetch evidence and provenance. Requires All versions and turns on version history.

A manifest on the right previews what will be transferred. Schedules, credentials, integrations, billing and active work stay in the source workspace; transferred pipelines arrive with their schedules off until you enable them. After the transfer, choose Stay here or Open destination.

Empty states

• No pipelines yet. A workspace with nothing in it shows a New Pipeline button.
• No matching items. Filters or a search excluded everything; Clear filters resets them.

The pipeline page

Open any card. The pipeline page has three layers: the hero, four section tabs, and the content of the selected section. Runs open inside the same page, so the hero and tabs stay put while you read a run.

Hero

• Breadcrumbs. Workspace › Pipelines › the pipeline. The pipeline crumb is a dropdown listing every pipeline in the workspace, so you can switch without going back to the list. On a run, a trailing crumb names the run.
• Icon. Click it to pick another icon. The colour is fixed per pipeline.
• Title and description. Click to edit; changes save when you leave the field. Placeholders are Untitled Pipeline and Add a pipeline description.
• Pills. Running while a run you started from this page is executing; Scheduled (a clock) when a schedule is set.
• Version chip. v2 with a history icon. Opens the version list; see Versions and changelog.
• Stats line. last ran 3 hours ago (red when the last run failed; links to that run), next run in 6h 12m or next run due on scheduled pipelines, and takes 14min to run (the average of the last five completed runs).
• Edit pipeline. Opens a composer addressed to Jason, with suggestion pills drawn from the pipeline’s specification, steps, parameters and last run. Placeholder What should change? Jason picks it up straight away.; send with Send to Jason or ⌘↵. A new chat scoped to this pipeline opens in the sidebar.
• Run Pipeline. Opens the run dialog. Disabled with the tooltip Pipeline has no active revision until the first version is activated. See Running a pipeline.

Add the retailer’s stock status next to the price, and flag rows where the promotion ended in the last 24 hours.

While a run started elsewhere (a schedule, a webhook, a teammate) is in flight, a banner sits under the hero: This pipeline is running · v2 · 4m 10s · 312 pages · about 9 minutes left, with View run.

When the workspace has no rows left this month, Run Pipeline opens Monthly collection cap reached instead of the run dialog. Adjust monthly cap takes you to usage settings. See Billing and usage.

Before the first version

A pipeline whose build has not finished shows a holding page instead of the sections:

You see	Meaning	Button
Jason is still building this pipeline	The build chat is active. The first version appears after Jason finishes testing it and the independent review accepts it.	Open build conversation
This pipeline isn’t ready yet — the build stopped	The chat stopped before a version was activated.	Open build conversation
This pipeline isn’t ready yet — no reviewed version	There is no build chat to return to.	Open Jason

Section tabs

Under the hero, four tabs switch the body of the page. Each tab keeps its own place in the URL, so links land on the right section.

Tab	Shows	Link
How it works	The specification rail and its pages: statement of work, steps, inputs, changelog and notes, settings.	#pipeline
Latest outputs <n> datasets	The datasets, files, dashboards, newsletters and integrations this pipeline feeds.	#outputs
Sources <n>	The sites read to build the latest datasets. Hidden until the first publish records a source.	#sources
Runs <n>	The newest run, with the runs rail down the side.	#results

The How it works rail

The left rail lists the pages of the specification. It collapses with Collapse how it works, resizes by dragging its edge, and becomes a select on small screens.

Entry	What it is	Page
Statement of Work	The plain-language contract: objective, scope, parameters, what the pipeline produces and the rules it follows. Select text to comment and send changes to Jason.	Statement of work and steps
Pipeline Steps	The step diagram of the version you are viewing, with a reading panel for each block. Shown once the version has a diagram.	Statement of work and steps
Inputs	Dataset inputs, editable value lists and parameter defaults.	Inputs and parameters
Changelog & Notes	Every version with its changelog line, and standing notes Jason reads whenever it works on this pipeline.	Versions and changelog, Settings reference
Settings	Schedule, Cache and Advanced (automatic repair).	Settings reference

If a link asks for a page the pipeline does not have (for example Pipeline Steps before a diagram exists) you land on the Statement of Work. A link with nothing specific lands on Latest outputs when the pipeline has published anything, otherwise on the Statement of Work.

Latest outputs

Latest outputs shows what the pipeline has published. When it feeds more than one thing, a rail on the left groups them:

• Files. Deliverables the pipeline builds on each run, with a count.
• Datasets. One entry per output dataset, with its row count once ready.
• Dashboards, Newsletters, Integrations. Resources wired to those datasets.

Dataset view. The header names the dataset (a link), a Dataset revision picker (1,274,880 rows · v3 (active) · 2 hours ago), an Export menu with Excel workbook (every worksheet) and CSV of this table (the table you are looking at), and Open dataset, which opens the dataset page at that revision. Below is the same browser as the dataset page: worksheets, sort, search and paging. Datasets that are still being written show Building…; a dataset with no publish yet shows No data published yet. See Dataset pages.

Deliverables view. Files the pipeline builds on each production run, as cards you can preview or delete (deleting removes every version of that file). Until the first run: Files appear here after the next production run.

Connected resources. A dashboard, newsletter or integration entry shows what it reads, its widgets or recipients, its schedule, when it last updated, and a button to open it.

An unbuilt or never-run pipeline shows Nothing published yet — run the pipeline to create its first output.

Sources

Sources lists every site the pipeline read to build its latest datasets, one card per domain, with the rows and URLs that came from it.

Option	Values	Default	What it does
Search	Free text, Search sources…	Empty	Filters the cards by domain.
Sort	Sort: Rows · Sort: URLs · Sort: Domain	Sort: Rows	Orders the cards.

Each card’s footer names the datasets that site feeds; clicking one opens the dataset filtered to rows from that source. The tab appears once a run publishes a dataset with per-row source attribution. Until then the section reads Sources appear here once a run publishes a dataset with per-row source attribution.

Runs

Runs opens the newest run inside the pipeline page, with a rail of every run on the left. Filter the rail, use the ↑ and ↓ keys to move between runs, and read each run’s Summary, Outputs, Steps, Activity and Logs. A pipeline that has never run shows No runs yet · Run the pipeline to publish its datasets. The run page is documented in Run detail.

The pipeline page refreshes itself: every 15 seconds while the tab is visible, every 3 seconds while Jason is working on the pipeline, and every 4 seconds for the runs list while a run is in flight. You do not need to reload.

What’s next