error fix
n8n Queue Mode Error: Fix Redis, Workers, Database, and Encryption Key Mismatches
Queue mode errors usually come from inconsistent main/worker configuration, Redis connectivity, database access, version mismatch, encryption key mismatch, or unsupported binary storage assumptions.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Queue mode errors usually come from inconsistent main/worker configuration, Redis connectivity, database access, version mismatch, encryption key mismatch, or unsupported binary storage assumptions.
Problem Pattern
Queue mode starts but executions fail or never complete because main and worker processes do not share the same infrastructure assumptions.
Key Facts
- Core components
- Queue mode involves main process, Redis, workers, and database.
- Required mode
- EXECUTIONS_MODE=queue must be set consistently.
- Shared secret
- Main and worker processes need the same encryption key.
- Database note
- n8n recommends Postgres rather than SQLite for queue mode.
Recommended Steps
- Confirm the main process and workers run the same n8n version.
- Confirm EXECUTIONS_MODE=queue is set where needed.
- Confirm N8N_ENCRYPTION_KEY is identical across main and worker processes.
- Check Redis host, port, credentials, and network access from all processes.
- Check database connectivity from both main and worker processes.
Verification
- Workers connect to Redis and database on startup.
- A production execution is picked up and completed by a worker.
- Worker logs no longer show encryption, Redis, or database errors.
Warnings
- Queue mode adds operational complexity; do not enable it just to fix a simple workflow bug.
- Different environment variables between workers can create confusing partial failures.
Common Mistakes
- Setting queue mode on the main process but not workers.
- Using different encryption keys across processes.
- Forgetting Redis credentials in one environment.
- Running workers against a different database or version.
Examples
N8N_ENCRYPTION_KEY=same
EXECUTIONS_MODE=queue
DB_TYPE=postgresdb
QUEUE_BULL_REDIS_HOST=redis
QUEUE_BULL_REDIS_PORT=6379
n8n version=sameFAQ
Why do workers start but fail executions?
They may connect to Redis but fail database access, encryption, binary data access, or version compatibility during execution.
Should I use queue mode for a small instance?
Usually no. Queue mode is for scaling execution processing and requires Redis, workers, database planning, and monitoring.