A media subscription renewal reminder has a deadline, and the queue does not know about it. The queue only knows delivery. With an at-least-once background job queue, retries and duplicate jobs are normal; the engineering decision is how replay is governed so one renewal cycle creates one reminder intent.
Short answer: make replay a recorded business decision. Derive one idempotency key from the renewal cycle, store the decision and outbound intent together, and route every later delivery through that record. Acknowledging a message is not evidence that the reminder happened.
This framing matters during incidents. A consumer can disappear after committing storage but before acknowledging its delivery. The next consumer must be able to say “already decided” without calling the mail provider again.
Define the replay subject before tuning the queue
For a renewal due at 2026-09-01T09:00:00Z , the reminder subject is one subscription, one renewal cycle, and one reminder kind. That tuple is the replay subject.…