error fix
n8n Worker Not Processing Jobs in Queue Mode
Check that main and worker processes use queue mode, share Redis, connect to the same database, use the same encryption key, and show healthy worker logs.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Check that main and worker processes use queue mode, share Redis, connect to the same database, use the same encryption key, and show healthy worker logs.
Problem Pattern
Queue mode breaks when the main process, workers, Redis, database, or encryption key are not aligned. Jobs can queue up while workers look healthy but cannot read credentials or pull execution data.
Key Facts
- Queue architecture
- Main creates executions, Redis queues them, workers pick them up, and workers read/write execution data through the database.
- Shared key
- Workers need the main instance encryption key to access credentials.
- Database recommendation
- Postgres is recommended for serious queue-mode deployments.
- Health signal
- Queue mode can expose worker health and readiness endpoints when configured.
Recommended Steps
- Confirm the main instance and workers are all running with EXECUTIONS_MODE=queue.
- Check Redis host, port, username, password, and database settings from both main and worker containers.
- Confirm workers connect to the same n8n database as the main instance.
- Verify N8N_ENCRYPTION_KEY is shared across main and worker processes.
- Review worker logs and health checks for Redis, database, credential, or concurrency errors.
Verification
- A test workflow execution is picked up by a worker.
- Redis shows jobs moving instead of permanently waiting.
- Worker logs show completed executions.
- Credential-using workflows succeed on workers, not only on the main process.
Warnings
- Do not scale worker count before confirming the database connection pool can handle it.
- A worker without the correct encryption key may fail when a workflow needs credentials.
- Filesystem binary data storage is not suitable for queue mode when workflows need persistent binary data.
Common Mistakes
- Starting the main process in queue mode but not the worker.
- Pointing workers at a different Redis or database.
- Missing N8N_ENCRYPTION_KEY on workers.
- Setting very low worker concurrency across too many workers.
Examples
Main EXECUTIONS_MODE=queue: yes
Worker command: n8n worker
Redis reachable from worker: yes
Database same as main: yes
N8N_ENCRYPTION_KEY same: yes
Test execution processed: yesFAQ
Why are jobs queued but workers idle?
Workers may not be connected to the same Redis queue, may not be in queue mode, or may fail readiness checks against Redis or the database.
Can this be fixed by adding more workers?
Only if workers are already healthy and capacity is the real bottleneck. Configuration issues get worse when you scale them.