{
  "id": 3602352,
  "title": "Durable Agent Workflows Need Idempotency Before They Need Checkpoints",
  "url": "https://urgent.news/2026/08/26/durable-agent-workflows-need-idempotency-before-they-need-checkpoints",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-26T21:00:02.000Z",
  "source": {
    "name": "HackerNoon",
    "slug": "hackernoon",
    "url": "https://hackernoon.com/durable-agent-workflows-need-idempotency-before-they-need-checkpoints?source=rss"
  },
  "original_language": "en",
  "account": "Durable agent workloads require idempotency to prevent duplication of damage when resuming from crashes or failures. Checkpointing alone is insufficient, as it cannot restore the external world. Every node's effect must be designed to be safe to run multiple times, or the node boundary may need to be adjusted. Each logical effect should have a unique identifier derived from the workflow run and business object, rather than generating random IDs for each retry. An \"effect ledger\" should record the intent, status, and attempt count for each effect. The ledger should use explicit states like PROPOSED, AUTHORIZED, REQUESTED, and CONFIRMED, with UNKNOWN to account for situations like timeouts.\n\nUsing the outbox and inbox patterns can help reduce gaps between durable state changes and external tool actions. Receipts should be stored as immutable records containing key details about the request and provider response. Human pauses, like approvals or webhooks, should also use stable keys to avoid creating duplicate requests on resume. Compensation for irreversible effects should not be treated as a simple rollback but rather as a separate logical step.",
  "summary": "Why checkpointed AI workflows still duplicate side effects, and how idempotency keys, effect ledgers, reconciliation, and compensation make resume safe.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}