Short answer: put renewal reminders on a durable main queue, cap redelivery, and move messages that still fail to a dead letter queue (DLQ). Then inspect the DLQ and redrive only after the underlying problem is understood. For a property-management deadline, that rule matters more than the queue brand: a reminder sent twice is annoying, but a reminder silently lost before the renewal date is worse.
I would choose one of two shapes. Use a broker-owned DLQ when the queue service can enforce redelivery limits and retain failed messages for inspection. Use an application-owned failure queue when the job needs richer quarantine state, custom replay policy, or a workflow engine around it. Both are valid. The invariant is the same: every attempt has an observable result, every retry is bounded, and the renewal operation is idempotent.
What should happen when a renewal task keeps failing?
Imagine a lease ending on 2026-11-30.…