> ## Documentation Index > Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt > Use this file to discover all available pages before exploring further. # Pipeline Monitoring > Monitor Zwiron jobs in real time — status, row counts, throughput, run history, tables, and transforms. Every pipeline (job) has a dedicated detail page that updates in real time while the pipeline is running. Open any pipeline from the **Jobs** list. *** ## Job statuses | Status | Meaning | | ----------- | ------------------------------------------- | | `created` | Queued — waiting for an available worker | | `running` | Actively syncing | | `completed` | All tables finished successfully | | `failed` | One or more tables failed after all retries | | `cancelled` | Stopped manually | *** ## Overview header The sticky header at the top of every job detail page shows: * **Source → Destination** — the two connected databases * **Status badge** — live status with a colored dot * **Sync mode** — Full Refresh, Incremental, or CDC * **Progress** — percentage complete and current throughput (rows/sec) * **ETA** — estimated time to completion while running * **Schedule badge** — next run time if a schedule is configured *** ## Tabs ### Overview | Section | Contents | | ----------------------- | ------------------------------------------------------------------------------------------ | | **Pipeline card** | Source, destination, sync mode, execution mode, workers, destination mode, schedule | | **Progress** | Live progress bar, rows moved, duration | | **Error message** | Displayed when the last run failed | | **Schema change alert** | Warning banner if a source column changed since the last run | | **Performance history** | Total runs, average duration, average throughput, failure rate (shown after the first run) | | **Notes** | Threaded team comments — see [Notes](#notes) | ### Tables Lists every table in the pipeline with its status (`running`, `completed`, `failed`, `pending`) and row count from the last run. **Filter by status** using the chip buttons above the list. **Add a table** to an existing pipeline: 1. Click **+ Add Table** 2. Search or select from the tables discovered on the source connection 3. Select one or more tables 4. Click **Add** **Remove a table:** 1. Tick the checkbox next to one or more tables 2. Click **Remove N** The table is removed from the pipeline. It is not deleted from the database. **Rerun a single table:** Hover over a table and click the refresh icon to rerun that table only, without affecting others. Or tick multiple tables and click **Rerun N**. ### Runs A full history of every pipeline execution: | Column | Description | | ----------- | ---------------------------------------- | | **Run #** | Sequential run number | | **Status** | Outcome of the run | | **Rows** | Total rows moved | | **Started** | Relative timestamp and any error message | Click any row to open the [Events log](/pipelines/events) filtered to that run. ### Schema Evolution When a source column is added, removed, renamed, or its type changes, Zwiron creates a **schema change proposal** and pauses. This tab shows all pending proposals. | Action | Effect | | ---------- | ----------------------------------------------------------------- | | **Accept** | Applies the change at the destination | | **Ignore** | Skips this change — destination stays as-is | | **Reject** | Reverts the destination schema to match the old source definition | A yellow badge on this tab shows the count of pending proposals. See [Schema Evolution](/concepts/schema-evolution) for the full guide. ### Transforms Shows all column-level transform rules configured for this pipeline. Transforms can rename columns, filter rows, or compute new values from existing ones. If no transforms are configured, click **Configure Transforms** to open the edit page. See [Transforms](/concepts/transforms) and the [Transform Function Reference](/concepts/transform-functions) for the available operations. ### Data Quality Shows the most recent [Validation](/pipelines/validation) report for this pipeline: * Structural, content, schema fidelity, semantic, and overall accuracy scores * Per-table breakdown (match / mismatch / error) * Semantic rules — pass/fail status for each custom assertion Click **Run Validation** to trigger a new validation run. See [Validation](/pipelines/validation) for the full guide. *** ## Notes Every pipeline has a threaded **Notes** section in the Overview tab. Notes are saved to local storage and visible to all organization members. * Write a note and press **⌘+Enter** (or **Ctrl+Enter**) to submit * Reply to any note to keep discussions threaded * Edit or delete your own notes Use notes to capture pipeline-specific context: known data quirks, links to tickets, or deployment history. *** ## Actions | Action | When available | Who can use | | ------------------------ | ---------------------------------------- | --------------- | | **Rerun** | After any completed or failed run | Editors, Admins | | **Cancel** | While the pipeline is running | Admins only | | **Retry Failed Tables** | When status is `failed` | Editors, Admins | | **Restart from scratch** | While running (overflow menu) | Editors, Admins | | **Pause** | While running, Temporal-backed jobs only | Editors, Admins | | **Resume** | After a successful pause | Editors, Admins | | **Edit** | Always | Editors, Admins | *** ## Alerting Configure where failure notifications are sent in [Notifications](/platform/notifications) — in-app and email today. [Webhooks](/platform/webhooks) are coming soon. *** ## Related * [Events](/pipelines/events) — granular per-run event log * [Schema Evolution](/concepts/schema-evolution) — handling source schema changes * [Validation](/pipelines/validation) — deep source-to-destination accuracy audit * [Transforms](/concepts/transforms) — column-level data transformations * [Analytics](/platform/analytics) — cross-pipeline aggregated metrics