Loading…
Loading…
Written by Max Zeshut
Founder at Agentmelt · Last updated Aug 19, 2026
The property of an agent runtime that lets a run survive crashes, restarts, and long asynchronous waits by persisting its full state and resuming exactly where it left off — potentially minutes or days later. Durable execution is what makes real Human-in-the-Loop (HITL) oversight practical: an agent can pause at an Approval Gate, persist its state, and wait for a human to respond hours later without holding a process open or losing context. The load-bearing mechanism is Checkpointing (Agent State) — snapshotting state at each step — which LangGraph provides natively and which dedicated durable-execution engines (Temporal, Restate, DBOS) provide as infrastructure. Without it, an agent that crashes mid-workflow either loses everything or re-runs side effects it already committed. Distinct from Stopping Conditions, which bound how long an agent runs; durable execution governs whether a paused or interrupted run can be faithfully resumed.
An invoice-approval agent processes a batch, hits an invoice over the auto-approve limit, and pauses for a manager's sign-off. The server redeploys overnight; the run's state was checkpointed, so when the manager approves at 9am the agent resumes from the exact paused step — no reprocessing, no duplicate payments, no lost context.