All 15 Background Jobs & Queues questions
More in Background Jobs & Queues
What is a background job in the context of a Node.js web application, and why can't long-running work simply happen inside a request handler? How does BullMQ (built on Redis) implement a job queue in Node.js, and what are its core building blocks? What is job idempotency, and why is it critical when designing background job processing? What is a cron job, and how would you schedule recurring background tasks in a Node.js application using node-cron or BullMQ's repeatable jobs? What is job concurrency in a worker process, and how do you configure it safely in BullMQ? How would you track and expose the progress of a long-running background job to the client that requested it? What are the trade-offs of using an in-memory job queue (like a simple array-based queue) versus a persistent, Redis-backed queue? What is a 'stalled' job in BullMQ, and what causes it? What is a dead-letter queue (DLQ), and how should a Node.js job-processing system use one? How do you implement job prioritization in a Node.js queue system, and when is it necessary?
Advertisement
Back to results for “Background Jobs & Queues”
Node.js › Background Jobs & Queues

What is the difference between a delayed job and a scheduled (repeatable) job in a Node.js job queue?

Beginner

Answer

A delayed job runs once, after a specified delay from when it was added (like 'send this reminder email in 24 hours') -- it's a one-time future execution. A scheduled or repeatable job runs on an ongoing recurring basis according to a cron pattern or fixed interval (like 'run this cleanup task every night at 2 AM'), continuing indefinitely until explicitly removed.
// Delayed job: runs once, 24 hours from now
await reminderQueue.add('send-reminder', { userId }, { delay: 24 * 60 * 60 * 1000 });

// Repeatable job: runs every night at 2 AM, indefinitely
await cleanupQueue.add('nightly-cleanup', {}, { repeat: { pattern: '0 2 * * *' } });
Real-world example An e-commerce platform uses a delayed job to send a 'complete your purchase' reminder email exactly 24 hours after a user abandons their shopping cart, while separately using a repeatable job to run inventory reconciliation every night, illustrating the two distinct use cases within the same queue system.

Common follow-ups: How would you cancel a delayed job before it fires, if the underlying condition that triggered it is no longer true?;How does a repeatable job's schedule interact with a queue's persistence if the whole system is down when it was supposed to fire?

Async Patterns;Cloud & DevOps
All 15 Background Jobs & Queues questions