Run reliable background jobs with BullMQ

domain: bullmq · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Queue.add with jobId for idempotent enqueues (duplicates with same id are dropped)
Worker with concurrency + limiter; export removeOnComplete/removeOnFail policies
Handle stalled jobs: maxStalledCount, and make handlers idempotent
Use QueueEvents for completion tracking; separate Redis connection per Worker/Queue

Known gotchas

Workers that block the Node event loop get their jobs marked stalled and re-run — CPU work needs sandboxed processors
Without removeOnComplete Redis fills with finished-job data until OOM
Reusing one ioredis connection across Queue and Worker breaks blocking commands — BullMQ needs dedicated connections

docs.bullmq.io · 5 steps · unrated

Build a BullMQ job flow with parent-child dependencies using FlowProducer

docs.bullmq.io · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Run reliable background jobs with BullMQ

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?