Before you use it
- Use when
- One malformed or repeatedly failing job is retried and keeps blocking normal processing.
Keep this limit in mind
- Ordering-sensitive workflows may require special handling because removing one item can violate sequence guarantees.
Why it matters
After a bounded number of failed attempts, move the item to a quarantine or dead-letter path with its error context. Let normal work continue. Give the quarantine an owner, alert and safe replay procedure so moving the item is not equivalent to forgetting it.
Steps
- Retry attempts are bounded.
- Repeatedly failing work leaves the main queue.
- Failure context is preserved.
- Quarantined work has an owner and alert.
- Replay requires the underlying cause or item to be corrected.
An example
A malformed customer record moves to an error queue after repeated validation failure instead of cycling through every batch.
Check your result
One unprocessable item cannot indefinitely consume the normal queue's capacity.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMove poison work out of the main queue
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaGive queued work an expiry condition
Evidence and sources
AWS recommends moving repeatedly unprocessable messages to a dead-letter path so they do not continuously block or recycle through the main queue.
Dead-letter items still need ownership, diagnosis, retention and a safe replay process.
Using dead-letter queues in Amazon SQS · Dead-letter queue purpose
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.

