Pipeline Events

Every pipeline run generates a structured event log — a timestamped record of every operation that happened, from table reads to worker assignments to errors. Events are visible on the job detail page under the Events tab for any run.

Event types

Pipeline-level events

Event	Meaning
`run.started`	Pipeline run began
`run.completed`	All tables finished successfully
`run.failed`	Run ended with one or more table failures
`run.cancelled`	Run was manually cancelled

Table-level events

Event	Meaning
`table.started`	A table began syncing
`table.partition.read`	A partition (chunk) was read from source
`table.partition.written`	A partition was written to destination
`table.completed`	Table finished successfully
`table.failed`	Table failed (error details included)
`table.retry`	Table sync is being retried (attempt N)
`table.schema_change`	Schema change detected for this table

Worker events

Event	Meaning
`worker.assigned`	A worker was assigned to a table
`worker.heartbeat`	Worker is alive and processing
`worker.disconnected`	Worker lost connection to control plane

Event details

Each event contains:

{
  "event": "table.partition.written",
  "table": "orders",
  "timestamp": "2025-03-12T08:14:22Z",
  "attempt": 1,
  "rows_read": 50000,
  "rows_written": 50000,
  "duration_ms": 1420,
  "partition": 3
}

Error events include the full error message and stack trace for debugging.

Error debugging

When a table fails:

Go to Jobs → select the job → History → select the failed run
Click the Events tab
Find the table.failed event for the failing table
Expand the event to see the error message

Common errors and their meanings:

Error	Cause
`connection refused`	Destination or source rejected the connection — check network rules and credentials
`column not found`	Source schema changed — check the Schema tab
`permission denied`	The database user lacks the required privilege — check the connector setup guide
`deadline exceeded`	The operation timed out — try reducing partition size or increasing timeout
`unique constraint violation`	Upsert failed because of conflicting primary keys — check for duplicate primary key values at source

Webhooks for events

Outbound webhooks for pipeline events are coming soon. See Webhooks for the planned design. Until then, use Notifications (in-app and email).

Last modified on July 13, 2026

Pipeline Monitoring Pipeline Validation

Getting Started

Guides

Core Concepts

Pipelines

Connectors

Platform

Support

Pipeline Events

Event types

Pipeline-level events

Table-level events

Worker events

Event details

Error debugging

Webhooks for events

​Event types

​Pipeline-level events

​Table-level events

​Worker events

​Event details

​Error debugging

​Webhooks for events

Event types

Pipeline-level events

Table-level events

Worker events

Event details

Error debugging

Webhooks for events