A job that fails once is a retry. A job that fails forever is a poison message. Without a dead letter path, that payload retries until it burns CPU, blocks a fair share of the queue, and pages the wrong people at 2 AM. I have seen a single malformed webhook JSON take down a worker fleet that was otherwise correctly idempotent and fairly sharded. Dead letter queues (DLQs), poison detection and safe replay are how you keep async failures from becoming a second outage.
I wrote this with help from AI tools and checked every example and claim myself. At Loop Origin we build Laravel and Node SaaS systems where queues are part of the product surface, not an afterthought. This is Part 3 of Reliable Queues & Async Work in SaaS. Part 1 covered idempotent jobs and exactly-once effects . Part 2 covered backpressure, fairness and tenant isolation .…