Background Jobs, Idempotency, and Retries Payroll calculation, report generation, imports, email batches, document generation, and integrations should not turn user-facing HTTP requests into long-running processes.
- - - - - Notify / query HTTP command Persist intent Enqueue job Worker Persist result > > > > > status
2026 course line • @nestjs/bullmq 12.0.0 integrates BullMQ with NestJS 12; BullMQ 6.x is the current major queue line.
• Jobs must be designed for retries. BullMQ explicitly recommends idempotent jobs so retrying a failed job leads to the same final state as a successful first attempt.
• Use stable business idempotency keys/job IDs where duplicate execution would be harmful, but remember queue de-duplication alone is not a complete business idempotency strategy.
Examples • Generate payroll PDF, import attendance CSV, synchronize government contribution tables, send approved PO to supplier integration, rebuild reporting projection.
• Recurring work should use the current BullMQ Job Scheduler API rather than removed legacy repeatable-job APIs in BullMQ 6. job key: payroll-run:<runId>:calculate
Worker checks database: - already COMPLETED? return existing result - PROCESSING stale? recover according to policy - otherwise claim work and continue
Retry is safe only when the operation is designed to survive duplicate delivery and partial failure. Official references: BullMQ idempotent jobs https://docs.bullmq.io/patterns/idempotent-jobs ; Job Schedulers https://docs.bullmq.io/guide/job-schedulers/ ; npm @nestjs/bullmq 12.0.0.
Enterprise systems are difficult because business invariants, approvals, auditability, effective dates, and permissions interact over long-lived data.
Restate the goal of “Background Jobs Idempotency and Retries” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: business workflow → invariants → permissions → transaction/audit → operational outcome. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Enterprise expansion blueprint for an HRIS/procurement/inventory/payroll-style system with modules, workflows, events, audit, and scaling triggers.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
Requisition -> Approval -> Purchase Order -> Goods Receipt -> Invoice
Invariant examples:
- received quantity <= ordered quantity
- finalized approvals are auditable
- closed orders reject new receiptsDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Background Jobs Idempotency and Retries” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Separate synchronous user requests from background work such as reports, imports, notifications, or payroll runs.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Microservices before module boundaries are understood
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.