dead-letter queue
A dead-letter destination retains work that exhausted normal processing or retry policy.
Use this when Repeatedly failing jobs block progress or disappear from view.
without the term
“Some background jobs fail forever and either retry endlessly or just vanish. Can we put the ones that keep failing somewhere we can look at and retry them later?”
with the term · How do you ask a model for dead-letter queue?
Add dead-letter handling for this job. Verify exhausted retries preserve diagnostic context and that replay does not duplicate completed side effects.
What is dead-letter queue?
After a job has failed its allowed retries, it moves to a separate queue with its error, where someone can inspect it, fix the cause, and replay it.
Why does dead-letter queue matter when vibe coding?
A retry loop can consume resources without making the failure actionable.
How do you do dead-letter queue?
Keep the error context and stable identity; define ownership, retention, and replay behavior.
What goes wrong with dead-letter queue?
Collecting failed jobs without a way to inspect or recover them.