Monitoring and recovery

Find and recover pipeline failures.

Review pipeline state, run history, data checks, runtime health and recovery controls in one workspace. The Assistant explains recorded evidence without taking write actions.

Run evidence Workflow illustration
Source countRecorded≠Target countMismatch
Discrepancy flaggedReview cutoff, watermark and merge keys
Review evidenceConfirm eligible repairRecheck

Core capabilities

Run evidence

See timing, rows read and written, publication state and table outcomes.

Data checks

Review independent source and final-target counts, saved watermarks and merge keys.

Evidence-based guidance

Ask PipePilot to separate measured findings from possible causes using saved evidence.

Data reconciliation

Catch discrepancies after each load.

For supported table loads, PipePilot compares fresh source and final-target row counts after publication. The dashboard flags a mismatch or measured rule risk for review; equal counts remain a limited signal, not proof that every value is correct.

Review the recorded counts, cutoff, watermark and merge keys before choosing the next action.

Reviewed discrepancy workflow · illustrative
  1. 01Compare countsFresh source vs final target
  2. 02Review the ruleWatermark, merge key and cutoff evidence
  3. 03Approve a repairEligible table reload requires confirmation
  4. 04RecheckA new independent audit records the result

PipePilot does not run Assistant-generated SQL or automatic repairs. A published load is not failed solely because its audit is unavailable.

Workflow

01

Start with the failed step.

Open the run or stream, inspect source, destination, runtime and checkpoint evidence, then choose an available recovery action.

Workflow01
01

Table-level batch outcomes

02

Source and destination stream status

03

Secret-redacted details

04

Assistant context for the selected error

Configuration and runtime evidence stay attached to the workflow.

Discrepancy review

02

Review, repair and recheck eligible tables.

A review queue surfaces confirmed count mismatches and measured incremental-rule risks. The Assistant explains saved evidence; the user decides whether to run an available repair.

Discrepancy review02
01

Dashboard flags for checks that need review

02

Explicit confirmation before a single-table repair

03

Atomic reload and fresh count check for eligible targets

04

No automatic diagnosis or repair

Configuration and runtime evidence stay attached to the workflow.

Next step

Plan your data workflow.

Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.

Request a DemoSign In