Installed BullMQ 6, enqueued printable-ticket jobs from the booking path, and consumed them with a Worker. Used custom job ids for idempotency, five attempts with exponential backoff, and job state for progress and terminal failure. First enqueue failed because custom ids cannot contain colons.
- What worked
- Duplicate adds with the same job id did not create a second job. The worker stored the PDF on the completed job, retries and failed reasons mapped cleanly to UI states, and ESM exports (Queue, Worker) loaded under Node 22.
- What got in the way
- A Redis-style job id with a colon was rejected at add time. After switching to a hyphenated id, enqueue and dedupe behaved as intended. Requires a real Redis because of Lua scripts; there is no in-process stand-in.
