Development

Idempotency and retries for agent writes

• A Retry and Backoff Contract Between an Agent and Its Tools
• An Outbox Table for Agent-Triggered Side Effects
• Fitting a Retry Budget to a Tool That Fails Slowly
• Idempotency at the Agent Tool Interface
• Idempotency Keys for AI Actions: Design and Verification
• Idempotency Keys for Payment APIs: Design and Verification
• Idempotent Write Attempts: Making Escalated Writes Safe
• Idempotent Writes for AI Agents: Catching a Retried Tool Call
• Letting the Model Choose the Key: Why It Usually Cannot
• Property Tests for Deterministic Keys: Same Input, Same Key
• Verifying Agent Tool Calls: Tests That Catch a Doubled Refund
• When a Tool Call Is Safe to Retry: A Decision Table by Effect
• A Dead-Letter Queue for Agent Tool Calls That Fails Validation
• A Deduplication Window: How Long to Remember a Key
• A Ledger Reconciler for Agent-Initiated Writes
• A Retry Budget per Agent Run, Not per Tool Call
• A Retry Budget per Tool Call: Counters, Backoff, Breaker
• A Staging Runbook for Retried Writes: Fixtures, Clocks, Money
• Alerting on Duplicate Writes That Slip Past Deduplication
• Alerting When Duplicate Writes Slip Through
• Asserting the Agent Changes Course After an Error
• Breaking an Agent's Retry Loop from Its Traces
• Choosing a Deduplication Store: Postgres Table, Redis Key or Both
• Choosing a Deduplication Window for Outbox Keys
• Claim Leases and Recovery for an Outbox Relay
• Compensating a Landed Write: Undo Paths for Agent Actions
• Compensating Transactions for Agent Writes: Undoing a Refund
• Contract Test for Idempotency: When a Tool Returns a Cache
• Dead-Letter Queues for Agent Tool Calls: Schema, Replay, Expiry
• Deriving Event Keys from Payload Fields: A Mapping Table
• Designing a Dead-Letter Queue for Agent Tool Calls
• Designing an Idempotency Contract for Agent Tool Calls
• Finding Duplicate Writes After a Retry Storm
• Idempotency Keys an Agent Can Safely Generate
• Making Retries Safe Before You Add Retry Hints
• Reading a 429 from a 503: Retry or Back Off
• Reconciling an Agent's Ledger Against the Downstream System
• Retry and Backoff Rules for Model API Calls
• Retry Hints in the Body vs Backoff in the Client
• Retry Hints vs Client Backoff
• Retry, Re-prompt or Escalate: A Decision Tree by Fault
• Setting a Statement Timeout and Retry Budget for Agent Queries
• Telling a Customer a Refund Was Issued Twice: Scripts and Data
• Testing Key Derivation: Property Tests for Idempotency
• When a Write Tool Returns Stored Result: Cache Expiry
• When the Agent Calls a Tool Twice: Detecting Duplicate Writes
• Writing the Outbox Row Inside the Agent Write Transaction