Dead Letter Queues for Failed Pipeline Records

By Michael Samuel Naeem · August 31, 2026 · 7 min read

If pipeline DLQ is not on your promote path today, you do not have dead letter queues for failed pipeline records — you have a checklist item.

Scenario worth designing for

One bad JSON line failed entire batch job for 6 hours.

Hard constraints

Compliance, latency, and cost caps are constraints — not afterthoughts. Design for rollback and audit evidence from day one.

Implementation walkthrough

Ship the smallest production slice of Dead Letter Queues for Failed Pipeline Records: one pipeline, one cluster, or one namespace — with rollback documented before widening scope.

Automate the boring steps so on-call never hand-edits pipeline DLQ settings during an incident. GitOps, versioned checkpoints, and pinned module versions beat runbook heroics.

How we validate before promote

Integration tests with production-shaped data volumes. Chaos or fault injection for dependency timeouts.

Replay one bad day of production traffic in staging before declaring pipeline DLQ done.

Production hardening

Pin versions, restrict break-glass access, and align client timeouts with server queue delays.

Review on-call pages tied to this topic after every incident — even minor ones.

Closing thought

Good dead letter queues for failed pipeline records work is invisible until it saves you from an outage, an audit finding, or a line item on the cloud bill.

Reference configuration

# SQS redrive policy — max receives before DLQ
{
  "RedrivePolicy": {
    "deadLetterTargetArn": "arn:aws:sqs:us-east-1:123:orders-dlq",
    "maxReceiveCount": 5
  }
}

Partition-level validation

Sample-only expectations miss full-partition violations — null keys on edge partitions, timezone-boundary duplicates, and late-arriving facts. Schedule full scans before promote and incremental expectations on every run. Store validation results as queryable tables so analysts see history, not only pass/fail in Slack.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Data Pipelines pipelines touch ingestion, serving, and finance. Document interfaces where pipeline DLQ gates hand off to downstream owners so failures are not bounced without context.

Operating pipeline DLQ at scale

After the first successful deploy of dead letter queues for failed pipeline records, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of pipeline DLQ settings with the on-call rotation — not only the primary author.

Further reading

• https://greatexpectations.io/
• https://docs.dagster.io/
• https://openlineage.io/