BullMQ: Missing lock for job / job stalled more than allowable limit Redis Origin: Data Last updated 5 Nov 2026

BullMQ: Error: Missing lock for job 42. moveToFinished / job stalled more than allowable limit

A BullMQ worker lost the lock on a job (it took too long or the event loop was blocked), so the job is considered stalled.

Exact message you may see Error: Missing lock for job 42. moveToFinishedjob stalled more than allowable limitBullMQ Missing lock for jobError: Job stalled more than allowable limitMissing lock for job moveToDelayed
Explore the map of this error Full error map →
Seen on: Redis Node.js

Meaning

Long CPU-bound jobs block the Node event loop so lock renewal fails. Fix by using sandboxed processors/worker threads, increasing lockDuration, avoiding synchronous heavy work, and ensuring Redis connectivity (maxRetriesPerRequest: null, no evictions: maxmemory-policy noeviction).

Common causes

  • CPU-bound job blocking the event loop
  • lockDuration shorter than job step
  • Redis latency/disconnects
  • Redis maxmemory-policy evicting BullMQ keys
  • Multiple workers with clock skew

⚡ Quick fix

  1. Use sandboxed processors (new Worker(name, "./processor.js"))
  2. Increase lockDuration and stalledInterval
  3. Set Redis maxmemory-policy noeviction

Detailed fix by platform

Node.js

  1. new Worker("queue", processor, { connection, lockDuration: 60000 });

How to diagnose

  1. Event loop — Blocked?
  2. Lock — Duration vs job time?
  3. Redis — noeviction?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

Bad file format reading the append only file / AOF corrupted — Redis: Bad file format reading the append only file: make a backup of your AOF file, then use ./redis-check-aof --fix <filename> (Redis)Bad file format readi…BUSY Redis is busy running a script — Redis: (error) BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE (Redis)BUSY Redis is busy ru…Celery with Redis: tasks run twice (visibility_timeout) — Celery: Task executed twice / Restoring unacked messages — Redis broker visibility_timeout shorter than task ETA (Redis)Celery with Redis: ta…Client output buffer limit reached (scheduled to be closed) — Redis: Client id=12 addr=10.0.0.5:51234 scheduled to be closed ASAP for overcoming of output buffer limits (Redis)Client output buffer …ClientClosedError: The client is closed (node-redis v4) — node-redis: ClientClosedError: The client is closed (Redis)ClientClosedError: Th…CLUSTERDOWN Hash slot not served — Redis Cluster: (error) CLUSTERDOWN Hash slot not served / The cluster is down (Redis)CLUSTERDOWN Hash slot…CROSSSLOT Keys in request don't hash to the same slot — Redis Cluster: (error) CROSSSLOT Keys in request don't hash to the same slot (Redis)CROSSSLOT Keys in req…DENIED Redis is running in protected mode — Redis: DENIED Redis is running in protected mode because protected mode is enabled and no password is set for the default user (Redis)DENIED Redis is runni…BullMQ: M…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.