Short answer: use this Node.js-style HTTP pattern to retry one specific failed background job: list the dead-letter queue (DLQ), select the eligible customer-support digest message, and redrive it to the main queue. Put a hard ceiling on attempts and make the digest worker idempotent. The queue can deliver the message again; it cannot decide whether sending the same digest twice is safe.
The useful comparison is not just which queue has retries. It is how quickly an engineer can inspect one failure, how many credentials and client libraries the recovery task needs, and how cleanly the system can recover after a bad run. For a weekly digest sent to active customers, operational recovery matters more than a benchmark number.
Why does a specific failed job need a DLQ boundary?
The tempting Node.js implementation catches an exception and immediately republishes the job.…