# A pipeline retry budget exhausts on a stuck message and the worker drops it silently

Canonical URL: <https://datadriven.io/problems/a-pipeline-retry-budget-exhausts-on-a-stuck-message-and-the-a958cbf9>

Domain: Pipeline Design · Difficulty: medium

## Problem

A pipeline retry budget exhausts on a stuck message and the worker drops it silently. The alternatives are worse: crash the worker, or write to stdout. The section's pattern is the dead letter queue: a separate durable destination where messages route after retries exhaust, with an envelope rich enough to recover from (original payload, failure timestamp, exception type, attempt count, correlation ID). Place the DLQ by adding one downstream of the worker and naming the envelope fields the pipeline writes.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/a-pipeline-retry-budget-exhausts-on-a-stuck-message-and-the-a958cbf9)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.