Protocol

Move poison work out of the main queue

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

See the ideaAn illustrative example

Give the repeated failure its own place.

Original Vedokrok holds a clipboard at a neighborhood parcel counter between an empty cream sorting tray and an empty amber review trayOne off-white example envelope with a red corner tab and a clipped blank context tag
After a bounded retry limit, separate repeatedly failing work with its context, owner, alert route and safe replay rule.

Keep the failed item and its context

Example: the job has reached its retry limit because a required field is missing. Its failure context is recorded; normal jobs wait behind it. Check ordering before moving it.

Follow the image, then make a version for your own work.

Has this item reached an agreed failure boundary?

Explore either choice, then decide what fits your situation.

Define my failure-review path

Stays on this page. Copy or save before leaving. Keep sensitive details out.

Fill each field to make your note.

Ordering-sensitive workflows need special handling before removing an item. Moving work to review does not fix it; ownership, error context, an alert and a safe resolution or replay path must remain.

Read the idea Save this pictureVedokrokSee the idea. Make your next move.

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

  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.

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.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingMove poison work out of the main queue

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.

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.

Read this idea as JSON · Release details