Topic starter
06/06/2026 2:28 am
TL;DR: AI agents that run for minutes or hours can lose state, repeat work, or fail mid-task unless their execution is durably recorded, according to WorkOS’s interview with Temporal co-founder Maxim Fateev. The governance question is not whether agents are clever, but whether their runtime assumptions survive crashes, retries, and intervention windows.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Maxim Fateev on why durable execution matters for AI agents”.
Key questions
Q: How should security teams govern AI agents that run long, multi-step workflows?
A: Security teams should require durable execution, full event history, and clear ownership for every multi-step agent workflow that touches sensitive data or privileged tools.
Q: Why do long-running AI agents need durable execution instead of normal retries?
A: Normal retries restart work but do not preserve state or execution history.
Q: What are the signs that an AI document workflow is too brittle for production use?
A: Warning signs include frequent 403 errors, broken formatting after edits, stale spreadsheet reads, overwritten human changes, and failure on larger files or multi-step tasks.
Practitioner guidance
- Map agent workflows to persisted execution states Identify every AI agent process that spans multiple steps, external APIs, or human approval gates, and define the state that must survive a crash or restart.
- Require step-level event history Make a complete execution history mandatory before agent workflows can touch production data or customer-facing actions.
- Bound agent authority across resume points Review whether an agent resumes with the same permissions it had before interruption, and decide whether that authority should be revalidated on restart.
Bottom line: AI agents that run across many steps need durable execution because crashes and restarts can otherwise erase state and repeat work.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 4:08 am
Durable execution is becoming the missing control plane for AI agents: agent reliability is now an identity and governance problem, not just an engineering one. When an agent runs across many steps, tools, and approvals, the question becomes whether execution state, permissioned actions, and traceability survive interruption. Practitioners should treat runtime continuity as part of access control for autonomous work.
A few things that frame the scale:
- 40 percent of financial and software companies have already deployed agentic AI systems, and deployments are expected to double by 2028.
A question worth separating out:
Q: What should teams do when an agent resumes after an interruption?
A: They should re-check whether the resumed workflow still has the right context, approvals, and permissions to continue. A paused agent may be acting on stale conditions, so resumption should not be treated as automatic continuity. The safer approach is to define which steps can resume freely and which must be revalidated before completion.
👉 Read our full editorial: Durable execution is becoming a control plane for AI agents