# Pipeline Run Monitor block

> Data pipeline run canvas with dependency-ordered replay and a human approval gate

ETL DAG run monitor: 6 run states, connection, test and model attachments, and retry or focus for the failed task. React Flow, ReUI IconTile, Badge, shadcn Tabs, ContextMenu, Progress. For orchestration dashboard, scheduled job status.

- Type: Pro block
- Category: [Flow](https://web.dev.reui.io/blocks/application/flow.md)
- Page: https://web.dev.reui.io/blocks/application/flow/flow-3
- MCP: `get_block("flow-3")`
- Built with: Alert, Alert Dialog, Avatar, Badge, Breadcrumb, Button, Button Group, Card, Context Menu, Dropdown Menu, Field, Icon Tile, Input, Item, Kbd, Popover, Progress, Select, Separator, Sheet, Spinner, Switch, Tabs, Toggle Group, Tooltip
- Installs with a ReUI Pro or Ultimate license; setup: https://web.dev.reui.io/docs/license-setup

## Best for

A replay with Run, Pause and Stop, a header progress bar, an approval gate that holds the run and a retry for the failed task

## Agent notes

- Replace `INITIAL_NODES`, `INITIAL_EDGES` and `PIPELINE` in data.tsx; `RUN_RESULT` copies their seeded statuses and `REPLAY_MS` paces each task
- Run plays `RUN_RESULT` back on a `setTimeout` in `tick`, and `retry` and `approve` force a success locally; no scheduler is called
- Task `params` edited in the inspector are saved on the node only, and `tick` never reads them

## When not to use

- A table of failed runs, each opening its error, retry attempts and payload: use [Failed Run Triage](https://web.dev.reui.io/blocks/solutions/agents/solution-agents-7.md) (`get_block("solution-agents-7")`)
- Editing an automation whose step cards show owner and last run status: use [Automation Builder](https://web.dev.reui.io/blocks/application/flow/flow-1.md) (`get_block("flow-1")`)

## Third-party libraries

- React Flow v12: [API reference](https://reactflow.dev/api-reference), [docs](https://reactflow.dev/learn), [llms.txt](https://reactflow.dev/llms.txt)
- Sonner v2: [API reference](https://sonner.emilkowal.ski/toast), [docs](https://sonner.emilkowal.ski/getting-started)

## Install

```bash
npx shadcn@latest add @reui/flow-3
```

## About Flow blocks

### When to use

- An editable node canvas for automation workflows or AI agent steps, with a side inspector per step
- A run view for a scheduled data pipeline: task states, retries and a human approval gate
- A driver map that ties initiatives to the input metrics and north star they are meant to move

### When not to use

- An overview page of KPI tiles, charts and work lists with no editable node graph: use the [Dashboard blocks](https://web.dev.reui.io/blocks/application/dashboard.md)
- A first run setup sequence that walks a new user through screens one at a time: use the [Onboarding blocks](https://web.dev.reui.io/blocks/application/onboarding.md)
- Operating live AI agent runs: tool permissions, approvals and evaluation reports: use the [Agents blocks](https://web.dev.reui.io/blocks/solutions/agents.md)

### Agent notes

- Graph edits stay in local `useNodesState` and `useEdgesState`; no block persists `nodes` or `edges`, so wire your own load and save
- Each block fills `h-svh` under its own header bar; swap it for a parent owned height when you mount it inside an app shell
- Requires `@xyflow/react`; flow-canvas.tsx imports its stylesheet and `FLOW_THEME` maps its colors onto your theme tokens

Every ReUI item has a twin like this one; the index is https://web.dev.reui.io/llms.txt. Agents with the ReUI MCP (https://web.dev.reui.io/docs/mcp) get the same guidance from the getters named above.