# Move poison work out of the main queue

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Move poison work out of the main queue

ID: MHC-D-RESEARCH-0534 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/move-poison-work-out-of-the-main-queue

One bad item should not get infinite turns at the front of the line.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- One malformed or repeatedly failing job is retried and keeps blocking normal processing.

### Avoid when

- Ordering-sensitive workflows may require special handling because removing one item can violate sequence guarantees.

### Explanation

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

1. Retry attempts are bounded.
2. Repeatedly failing work leaves the main queue.
3. Failure context is preserved.
4. Quarantined work has an owner and alert.
5. Replay requires the underlying cause or item to be corrected.

### Example

A malformed customer record moves to an error queue after repeated validation failure instead of cycling through every batch.

### Check

One unprocessable item cannot indefinitely consume the normal queue's capacity.

### Limits

- Ordering-sensitive workflows may require special handling because removing one item can violate sequence guarantees.

### Evidence and sources

- supports: AWS recommends moving repeatedly unprocessable messages to a dead-letter path so they do not continuously block or recycle through the main queue. — RS-71B5A64878ACBB5F. Dead-letter items still need ownership, diagnosis, retention and a safe replay process. (Dead-letter queue purpose)
- RS-71B5A64878ACBB5F: Using dead-letter queues in Amazon SQS — https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html

No review details supplied.
