We Trust AI Agents That Break Every Day - Shy Ruparel, Temporal
핵심 요약
Durable execution platforms bridge the gap between daily agent usage and production reliability by maintaining state and event history across worker crashes without re-running token-heavy LLM calls.
하이라이트
Corporate productivity gains from agentic AI reached 3 trillion dollars in 2025, with financial services leading at 94% adoption.
Daily agent usage doubled from 47.3% to 80.8% over the course of a year, while only 49.1% of teams operate agents in production.
Over 85% of engineers trust agent output at least somewhat, yet 41.1% encounter system issues daily and 16.4% experience them hourly.
Tracking state and debugging rank as the top two blockers for engineering team productivity, bypassing model limitations entirely.
Durable execution allows code to run to completion even when processes crash, preserving state and event history without requiring custom recovery code.
타임라인
Corporate AI Adoption and Industry Gaps
Financial operations run on long-running workflows spanning multiple systems and days, involving real money that leaves no room for error. A survey of engineers with substantial industry experience highlights that despite high adoption rates, a significant operational gap separates daily use from reliable production deployment.
- Corporate productivity gains from AI agents totaled 3 trillion dollars in 2025 according to a KPMG survey.
- Financial services lead adoption with 94% of fintech firms treating AI as core to operations.
- A survey of 554 experienced engineering professionals revealed four major gaps in agent deployment.
Usage Versus Production and Trust Versus Reality
A stark contrast exists between how widely agents are used and how often they successfully reach production. High confidence in agent outputs clashes directly with frequent system failures occurring on a daily or hourly basis, proving that technical skill alone does not eliminate system instability.
- Daily agent usage jumped from 47.3% to 80.8%, but only 49.1% of teams run agents in production.
- Eighty-five percent of surveyed engineers trust agent output at least somewhat.
- Fourteen percent of teams encounter agent issues daily, and 16.4% experience system failures every hour.
Deployment Speeds and Reliability Obstacles
Large regulated enterprises require strict audit trails, approvals, and guaranteed transaction handling, which extends deployment timelines to months. State management and debugging emerge as primary operational bottlenecks, forcing engineers to write extensive auxiliary code unrelated to core business logic.
- Half of all teams transition an AI prototype to production in hours, whereas large enterprises with over 5,000 employees often require months.
- Tracking state across services limits productivity for 35.7% of teams, while 30.9% struggle with debugging.
- Twenty-two percent of survey respondents lose progress and must repeat work due to application crashes.
Durable Execution and Live Demonstration
A live payout workflow demonstration shows how killing background workers mid-process fails to disrupt ongoing transactions. Signals such as human approvals are safely captured and processed upon worker recovery, eliminating the need to waste expensive LLM tokens or rebuild application state from scratch.
- Durable execution ensures workflows run to completion even when individual workers crash.
- Temporal records every state change, tool call, and human approval signal in an immutable event history.
- Production environments like OpenAI's codex and Replit utilize durable execution to prevent catastrophic workflow failures.
설명
Temporal's State of Development survey found that 80.8% of engineers use agents daily, but only 49.1% run them in production. Developer advocate Shy Ruparel walks through the four gaps behind that number (usage vs. production, trust vs. reality, prototype vs. enterprise, seeing vs. recovering), then demos a $2,500 payout workflow with a local model that survives having its workers killed mid-flight, without losing state, repeating tool calls or re-spending tokens. Chapters: 0:00 Intro 0:34 Finance runs on long-running workflows 2:05 The State of Development survey 3:16 Gap 1: Usage vs. production 4:33 Gap 2: Trust vs. reality 7:18 Gap 3: Prototype vs. enterprise 8:55 Gap 4: Seeing vs. recovering 10:53 Demo: a payout that survives a crash 13:06 Durable execution explained 18:12 What the demo solved 20:10 Who runs this in production 20:50 Wrap-up Shy Ruparel https://temporal.io Join us in SF for the second annual AIE CODE summit: https://aie.codes our last flagship summit of 2026. Applications live now!
