Pipelines
Pipeline list
Scan pipeline status, filter and sort the Pipelines page, and start, pause or archive several pipelines at once.
The Pipelines page lists every active pipeline in the account, with live status, throughput and lag. Use it to find what needs attention, to start or pause pipelines in bulk, and to open a pipeline's detail page. Select New pipeline to open the wizard.
The page updates live as agents report. The status tab and search text are kept in the page address, so you can share or bookmark a filtered view.
Status
The status tabs across the top filter the list, and each shows a count.
| Tab | Shows |
|---|---|
| All | Every active pipeline. |
| Healthy, Degraded, Failing | Pipelines with that status. |
| Issues | Every pipeline that needs a look: Degraded, Failing, Stale, Restarting and Preparing to load. Paused and loading pipelines aren't included. |
| Archived | Archived pipelines. See Lifecycle. |
Each row has a status dot, and the detail page shows a chip with the same word.
| Status | Dot color | Meaning |
|---|---|---|
| Healthy | Green | Streaming changes normally. |
| Degraded | Amber | Running with elevated lag or errors. |
| Failing | Red | Not making progress. The row shows the error. |
| Loading | Indigo | The initial load or a reload is copying rows. The pipeline isn't streaming yet. |
| Preparing to load | Indigo | Shown for a moment after you accept a reload, until rows start to copy. |
| Restarting | Indigo | Automatic restart is bringing the pipeline back from its saved position. |
| Paused | Gray | Stopped by you. It holds its position and does nothing until you start it. |
| Stale | Amber | The agent that runs the pipeline is offline, so the last reported status is no longer live. |
Find a pipeline
- Type in Filter pipelines… to match a pipeline's name or id.
- Select a column heading to sort by it. By default the worst status comes first, and within a status the highest lag.
- When you arrive from an agent's pipeline count, a banner says
Showing pipelines on agent <name>. Select Clear to see all pipelines again.
Read a row
| Column | What it shows |
|---|---|
| Pipeline | A status dot, the source and target logos, the name, and the source and target connections. A failing pipeline shows its error here. |
| Events / sec | Changes per second. |
| Data / sec | Data per second. |
| Recent throughput | A sparkline of recent changes per second, or a progress bar while the initial load runs. |
| Lag | The last measured end-to-end lag, then goal <value>. The color compares the lag with the pipeline's lag goal. See Lag, spool and log retention. |
| Error rate | Failed applies as a percentage. Any value above zero is red. |
| Tables | How many tables the pipeline replicates. |
Chips beside the name flag a pipeline that can't run: unassigned has no agent, and agent offline has an offline agent. An amber loading alongside <n> chip says other pipelines are loading on the same agent, source database or target database. Hover to see which ones. When a pipeline is Failing or Stale, the throughput values show –.
While an initial load runs, the row shows Loading <percent>% with the rows copied, the rate and the tables done. A load waiting for its agent reads Queued, with the pipelines it waits behind. See Initial load.
Start, pause and archive from the list
A paused pipeline whose agent is online shows a Start button on its row. For a pipeline that runs on two agents, both must be online.
To act on several pipelines:
- Select the checkbox on each row.
- In the bar at the bottom, select an action:
- Pause selected, and confirm with Pause all. Replication stops on every selected pipeline until each is started again, and changes keep accumulating at the sources.
- Archive selected, and confirm with Archive. Pipelines that are replicating on a live agent are refused, so pause them first.
- Start selected, which starts them without a confirmation.
The page reports the result, for example Started 2 · 1 failed: <reason> (failed pipelines stay selected). Fix the reason and try again.
Empty and error states
- A new account shows No pipelines yet. with Create first pipeline. You don't need a project or a saved connection first, and you can add an agent during setup.
- If the control plane can't be reached, the page shows
Couldn't load pipelineswith a retry, rather than an empty list.
