The short answer
For a game renewal notice, the queue is not the system of record. Store the reminder intent and its business deadline in durable state, enqueue a small wake-up job, and make the worker re-check that state before sending. The retry path should preserve the deadline, count attempts, quarantine poison messages, and expose enough history for an operator to recover a missed notice.
The useful unit is therefore a recoverable reminder, not a delayed message. A queue can wake a worker; it cannot decide whether a renewal is still eligible after a subscription change, a clock correction, or an outage.
In a Node.js service, I would keep the event-loop work small and push delivery to workers, but I would make the same storage and recovery rules apply no matter which queue implementation sits behind the interface. The deadline is a business fact. The delivery timestamp is an attempt.…