Changelog

Dead-letter queues

A message that always fails used to behave differently on each cloud: retried until SQS retention ended, retried for days on Pub/Sub, parked in a Service Bus subqueue nothing read, or retried forever locally. Now a Queue can name another Queue as its dead-letter target:

alien.ts
const failed = new alien.Queue("tasks-failed").build()
const tasks = new alien.Queue("tasks").deadLetter(failed, { maxAttempts: 5 }).build()

After maxAttempts failed deliveries (5 to 100, default 5), the message moves to tasks-failed with its payload. The target is a normal Queue: link it, receive from it, or trigger a Worker from it.

  • Approximate count: SQS counts every receive and Pub/Sub is best-effort, so a message can move a little early or late
  • No redrive call: to retry a message, send it to the original queue again
  • Frozen queues: adding it to an existing queue needs a setup rerun, which updates the same queue in place and keeps its messages
  • attempt on Google Cloud: receive and a Worker's queue trigger report Pub/Sub's delivery attempt for a queue with a dead-letter queue
  • alien.toml: dead-letter = { queue = "tasks-failed", max-attempts = 5 }

Read the docs →