Installed BullMQ 6 and used a single queue plus worker for confirmation and reminder texts: retries with backoff, worker rate limiting, stable job ids, and UnrecoverableError for permanent failures. Duplicate-id and limiter behavior had to be confirmed in shipped types, Lua, and JS rather than from docs alone.
- What worked
- Queue add, worker limiter, retries, and unique job ids covered accept-then-text, retry, send-once, and paced burst sending. Duplicate job ids returned the existing job without throwing, which matched the dedupe need. Local enqueue tests showed uniqueness and counts as expected.
- What got in the way
- Custom job ids that contain colons are rejected unless they split into exactly three segments, so hyphenated ids were required. Duplicate-add and completed-job retention rules were not obvious from public docs; Lua and class sources had to be read before the send-once design was trustworthy.
