Three Major Improvements for Pipelines

Cloudflare is shipping three significant updates to its Pipelines service, which ingests streaming data via Workers or HTTP endpoints, transforms it with SQL, and writes to R2 as Apache Iceberg tables.

Dropped Event Metrics & Observability

Stream events that don't match the expected schema are now surfaced with detailed error metrics. When ingestion occurs but events fail during delivery to the sink, a new dashboard tab displays dropped events grouped by error type: missing_field, type_mismatch, parse_failure, or null_value.

Beyond the UI, you can query dropped events programmatically via the new pipelinesUserErrorsAdaptiveGroups GraphQL dataset, allowing you to integrate error tracking into your monitoring systems and trace issues back to the source.

Typed Pipeline Bindings for Compile-Time Safety

Previously, sending data from Workers to Pipelines used a generic Pipeline<PipelineRecord> type, meaning schema mismatches were only caught at runtime as dropped events. Running wrangler types now generates schema-specific TypeScript types for your Pipeline bindings, enabling TypeScript to catch missing required fields and incorrect types at compile time before deployment.

Simplified Setup Workflow

The new wrangler pipelines setup command introduces a Simple setup mode that applies recommended defaults and automatically creates the R2 bucket and enables R2 Data Catalog if needed. Previously, this required multiple manual steps. Validation errors during setup now prompt inline retries rather than restarting the entire process.

For detailed walkthroughs and GraphQL query examples, refer to the Pipelines documentation.