A web request can accept work that will complete later, but acceptance is a durable state transition rather than a promise of instant success. This track follows a permit-report generator whose queue, worker, database, and browser can fail independently. It keeps job IDs and progress resources stable, treats duplicate delivery as normal, quarantines records that cannot succeed, and makes cancellation and scheduled overlap explicit. Every retry path is tied to a business effect that can be verified.
Topics in this track
- Job Admission, Idempotency, and Status Resources — Return a durable operation identity and a truthful state when asynchronous work is accepted.
- Worker Leases, Retries, and Duplicate Effects — Assume a queued message can reappear, and protect the business effect before acknowledging it.
- Poison Job Quarantine and Replay Control — Stop a permanently failing job from cycling forever and make repair or replay auditable.
- Scheduled Job Overlap, Cancellation, and Compensation — Define what happens when runs overlap, users cancel, or effects already escaped the system.
Prerequisite paths
Background Jobs and the Outbox Boundary; Accepted Operations and Status Resources.
Neighbor track
Abuse-Resistant Public Endpoints.
Practice path
Build Project: permit report job recovery and check decisions in Web Development: jobs and abuse decisions quiz.
Further connections
Extension Background Events and Durable State.
Further connections
FastAPI Lifespan, Background Work, and Delivery State.
Further connections
Laravel After-Commit Jobs and Outbox Recovery.
Further connections
Flask Async Views and Durable Background Work.
Further connections
Rails Active Job After-Commit and Outbox Recovery.
Further connections
CMS Publish Events, Cache, Search, and Rollback.