background-jobs
Installation
SKILL.md
Background jobs and concurrency
Work that leaves the request, and state that more than one thing touches at once. Both fail quietly: a job accepted into memory vanishes on deploy; two workers both think they won. Pick the file:
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
| An endpoint that starts long work and lets the client track it | ASYNC-APIS.md |
| Queues, workers, schedulers, crons, retries, dead letters | WORKERS.md |
| Paid or irreversible provider calls: submission intent, uncertain outcomes, reconciliation and restart | EXTERNAL-SIDE-EFFECTS.md |
| Multi-step work that runs for minutes to days: durable steps, replay rules, waits for events and people, compensation, flow control per tenant, progress streaming | DURABLE-WORKFLOWS.md |
| Races, row locks, isolation, deadlocks, "only one at a time", across one process or many | CONCURRENCY.md |
For jobs that call paid AI APIs, also read the ai-features skill's AI-JOBS.md; for idempotency keys and status codes, the api-design skill.