We Trust AI Agents That Break Every Day - Shy Ruparel, Temporal
Summary
The talk addresses the significant gap between the daily usage of AI agents (80.8%) and their deployment into reliable enterprise production systems (49.1%). The core challenge is that while agents are trusted (85.5% trust output), they frequently fail (41.1% experience daily issues). The solution presented is Durable Execution, a Temporal concept that ensures workflows survive worker crashes, maintaining state, preventing the re-spending of LLM tokens, and eliminating the need for complex, unrelated crash recovery code. This approach is critical for building reliable, long-running financial workflows.
Key takeaways
-
Usage vs. Production Gap
5:16
While 80.8% of surveyed engineers use agents daily, only 49.1% are running them in production, indicating a major reliability hurdle (30% gap).
-
Trust vs. Reality
8:16
Despite 85.5% of users trusting agent output at least somewhat, 41.1% report hitting agent issues daily or worse, proving that failure must be accounted for in production design.
-
Reliability Gap: Seeing vs. Recovering
20:40
The top blockers for productivity are state tracking (35.7%) and debugging (30.9%), highlighting that state management is the most critical aspect of enterprise AI deployment.
-
Durable Execution Solution
Durable execution allows a workflow to survive process crashes (e.g., timeouts, memory errors). State and progress are maintained in an event history, ensuring that AI activities and tool calls are executed only once, saving costs and complexity.
Technical details
-
Durable Execution
A Temporal concept where code runs to completion even if the worker process fails. State survives, progress survives, and every step is recorded in an event history. This allows the system to resume from the last successful event without re-running activities or re-spending LLM tokens.
-
Workflow Structure
Workflows are deterministic, while non-deterministic or side-effecting actions (like LLM calls or bank API calls) are run within dedicated 'Activities.' The human approval or rejection is captured as a 'Signal,' which is recorded in the history and processed even when the worker is offline.
-
State Management
Temporal manages workflow state using plain variables (fields), eliminating the need for external databases or caches for state persistence, which was identified as a major blocker.
-
LLM Integration
1200s
The demo used a local LLM (Qwen 36B/9B) within a payout workflow. Durable execution ensures that the agent's work (e.g., drafting a brief) is retained and not regenerated upon failure, addressing cost concerns (8 out of 10 people cite cost limits).
Mentioned resources
Channel & topics
Watch on YouTube · Back to latest
This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.