Short answer: keep the reminder in a durable database, use delayed queue messages only inside the seven-day window, and let a small promoter bring later reminders into that window. Make the webhook send idempotent, preserve the same delivery key across retries, and send exhausted work to a dead letter queue for bounded redrive.
That trade-off matters in fintech because a missed reminder is visible to a user, while a duplicate webhook can trigger a second notification, charge, or ledger-side action. The queue is transport. It is not the record of what the customer asked for.
I care about the recovery path first. A timer that fires on a quiet day is easy. A worker that sends successfully and dies before acknowledgment is the case that wakes someone up.
The incident lesson: one delivery key must survive every retry
The dangerous sequence is short: a consumer receives a message, the notification endpoint accepts it, and the process exits before the queue acknowledgment reaches the broker.…