Kiran Prakash published an architectural article on martinfowler.com on 10 November 2026 explaining how durable execution can help agents carry out tasks spanning days or weeks. Its purchasing example separates brief actions from long waits for approvals, supplier replies and deliveries, during which processes can crash and messages can be delayed or duplicated.[1]
The article describes a runtime that persistently records the inputs and outputs of steps interacting with external systems, including model calls and tool execution. After a crash, replay starts the program again: steps with recorded outputs return those outputs, while local code runs again to reconstruct state. In the Temporal example, model decisions and tool calls are activities; approval waits use a separate workflow primitive.[1]
Prakash says the example was built on Temporal and Cloudflare Workflows. The excerpt describes a recorded Temporal run in which the process stopped while awaiting approval, then resumed without repeating earlier completed actions. This is the author's account of an example, rather than an independently reproduced test or a product release announcement. The source also identifies retries that duplicate orders, unseen external outcomes, changing prices, code changes and untrusted input as concerns; the saved text ends before their detailed treatment.[1]
[1]: https://martinfowler.com/articles/durable-execution-agents.html
Sources
Check or correct this page
Verification record
The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.
5709f8db273a0ef2a0eaf02136300f60b15d4944b6b0372a15af4fd043b15be7