Bull queue workers appear healthy but jobs do not process until Redis connectivity is explicitly validated in deployment
Problem
Queue-backed async processing using Bull looked configured correctly, but actual job execution depended on deployment-level Redis connectivity being cleanly established. The fix required validating REDIS_URL, runtime reachability, and queue boot logs rather than assuming queue initialization implied working Redis transport.
Error Output
Jobs enqueued but not processed consistently, or workers appear connected without stable execution.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Treat Redis transport validation as a deployment prerequisite, not just queue initialization
Application boot can make queues look initialized while Redis connectivity, network routing, or deployment environment still prevents reliable worker execution.
Trust Score
1 verification
- 1
Validate REDIS_URL at runtime
Validate REDIS_URL format and environment injection at runtime.
- 2
Log Redis connection success
Log explicit Redis connection success before worker startup.
- 3
Log worker registration
Log worker registration and first job acquisition.
- 4
Add startup health check
Add a startup health check that performs a lightweight queue operation.
- 5
Fail fast on unreachable Redis
Fail fast when Redis is unreachable instead of allowing a half-healthy boot state.
Validation
Workers connect, accept jobs, and complete a real end-to-end queue task after deployment.
Verification Summary
Sign in to verify this fix