Create BullMQ queue processors and services with session propagation and retry behavior.
npx skills add https://github.com/Zoppy-crm/.github --skill queue-processor
Please help me install this Agent Skill. Skill: queue-processor Source: https://github.com/Zoppy-crm/.github/tree/main/skills/backend/queue-processor Command: npx skills add https://github.com/Zoppy-crm/.github --skill queue-processor
This guide removes guesswork and prevents common mistakes when adding BullMQ queue processors and QueueServices to zoppy-api by documenting required session propagation, locking patterns, registration rules, and logging/retry expectations so background jobs run correctly and reliably.
Create a Request-scoped QueueService and a Processor that calls await this.setSession(job) first, configures concurrency and lockDuration, uses the appropriate QueueJobEnum and QueueEnum, and registers the queue and processor in the correct module so jobs process reliably.
High-intent search queries and answers about installing and using this skill.
To propagate session context in BullMQ background jobs, call `await this.setSession(job)` at the start of the processor's process method. This ensures the job executes with the correct request-scoped session data and retry behavior.
To prevent duplicate job consumption in NestJS BullMQ processors, register each queue processor in exactly one pipeline module. This single-module registration rule stops multiple consumers from processing the same background job concurrently.
You need Redis locks for BullMQ queue processing when extending `ProviderQueueProcessorBase` to handle exclusive per-company or per-provider jobs. Configuring `lockDuration` ensures jobs expire correctly and prevents overlapping exclusive processing.
The best way to configure concurrency and retries for BullMQ processors is to extend `QueueProcessorBase`, use centralized enqueue helpers with retry presets, and re-throw errors after structured logging to trigger automatic BullMQ retry behavior.
Yes, you can use BullMQ queue processors for asynchronous provider syncs, message sending pipelines like WhatsApp or SMS, workflow execution steps, and campaign processing by creating standardized QueueService and Processor implementations.
BullMQ background jobs fail to execute with the correct session when `setSession(job)` is not called at the beginning of the process method. Always invoke this first to establish proper session propagation before processing logic.
zinohomeProcess background jobs with BullMQ and Redis queues.
zinohomeDesign background job systems with queue integration, retry policies, and idempotency.
TheBushidoCollectiveEnforce authentication, authorization, logging, and transformation in NestJS applications.
tuliosouza99Run asynchronous distributed background tasks and scheduled jobs in Python.
