Node.js Background Job Queue — 3 Rules for Scheduled Cleanup Retries

Node.js background job queues for cleanup and user reminders require durable structures and idempotency keys to ensure retry safety. Implement a bounded retry queue with a deliberate backoff schedule and a dead-letter queue for exhausted messages. For weekly digests, use lean payloads containing account identifiers and operation keys. To prevent duplicate reminders or failed cleanups, treat expiration as a conditional state transition and ensure operations are safe to repeat, avoiding unbounded retry loops during provider outages.