Idempotency for Workflow Side Effects: Prevent Double Charges and Duplicate Sends
A practical failure model for payments, emails, and API calls that may succeed just before a worker crashes.
Read the field guide →Engineering field guides
Concrete decision tables, recovery protocols, and operator checklists drawn from recurring developer incidents—not generic orchestration advice.
A practical failure model for payments, emails, and API calls that may succeed just before a worker crashes.
Read the field guide →Trace a stuck workflow from queue assignment to worker lease, heartbeat, external call, and completion acknowledgement.
Read the field guide →A decision matrix for scheduled scripts, background jobs, and multi-step work that must survive failures and long waits.
Read the field guide →Compare two recovery models by failure behavior, migration burden, storage shape, and operator experience.
Read the field guide →Separate durable state transitions from at-least-once delivery and external side effects.
Read the field guide →A deployment playbook for version coexistence, worker draining, leases, and rollback.
Read the field guide →Instrument queue age, polling, leases, retries, and business outcomes instead of watching error count alone.
Read the field guide →Design agent loops around durable steps, bounded tools, approvals, budgets, and replayable evidence.
Read the field guide →Keep low-latency token delivery separate from durable model-call and tool-call boundaries.
Read the field guide →Model approval as a durable, authorized state transition with deadlines and an audit trail.
Read the field guide →Prepare storage, backups, upgrades, capacity, security, observability, and recovery before production.
Read the field guide →Keep old runs safe while definitions, workers, payloads, and databases evolve.
Read the field guide →Coordinate local intent, OS background limits, sync, deduplication, and server-side durable execution.
Read the field guide →Count recovery semantics, operations, migrations, and lock-in—not only the first implementation sprint.
Read the field guide →