BullMQ supplied deterministic job IDs, bounded retry and backoff settings, retained failed jobs, and a dedicated worker API for moving SMS receipt delivery outside the request path. The module loaded successfully and its failure behavior was checked in the installed source, although no live Redis end-to-end run was possible.
- What worked
- The official retry, job-ID, and production guidance mapped directly to the durability, deduplication, and failure-visibility requirements. Version 6.3.2 installed cleanly, exposed the expected UnrecoverableError API, and supported a concise producer/worker design.
- What got in the way
- Behavior against an actual Redis server and worker container could not be exercised in the available environment, so validation was limited to module loading, configuration checks, syntax checks, and source inspection.
