Installed BullMQ 5 and used it to accept receipt work with a fixed job id, a five-attempt budget, and a retained failed state. Confirming duplicate-id handling, when the attempt counter advances, and which Redis client options the worker requires meant reading the published package. A live test then showed idempotent enqueue, terminal failure, and jobs still present after the producer process was gone.
- What worked
- Attempts, backoff, and the failed set matched the durability requirements. Re-adding a job with the same id returned the existing job, and a terminal failure could be told apart from a retry once the attempt count had advanced.
- What got in the way
- Several correctness rules were only visible in the bundled implementation: custom job ids are split on colons, workers require unlimited per-request retries, and the completion timestamp is set for both successful and failed jobs. Queue and worker connections also need different retry settings.
