Production agents need durable jobs, not in-loop retries, when side effects matter
Delicious-Energy7016 · reddit · 2026-07-29
A production agent that can mutate real systems exposed a reliability trap: retry logic inside the agent loop dies with the container.
- In demos, wrapping tool calls with .withretry() looks fine.
- In production, long LLM runs can outlive the process; if the container recycles mid-run, in-memory retry state disappears.
- That can lead to calls never firing or firing twice.
- The fix is to treat side-effecting tool calls as durable jobs: persistent retries, backoff, idempotency keys, and a record of what actually happened.
- The author now hands off anything touching money or external state to durable execution instead of retrying in-loop, and asks how others handle it (Temporal, Inngest, queues, or custom infrastructure).
Related event: Production Agent Pitfalls: Retry Is Not Safe Resume(2 posts)→
More from coding & agent
- Tencent Releases UI-Mate-27B, a Desktop GUI Agent Model — tencent · 2026-08-24
- Comparing AI Subscriptions: DeepSeek API vs. Claude Pro vs. Local LLMs — Unlikely_Bluejay5392 · 2026-08-24
- Claude Code introduces 'Remote Control' feature to boost coding efficiency — rohanpaul_ai · 2026-08-24
- rauchg lays out fx extension philosophy: MCP, Skills, Plugins and Unix composition — AccBalanced · 2026-08-24
- Netflix details its production LLM judge: hundreds of thousands of recommendations scored weekly — omarsar0 · 2026-08-24
- smolvm passes Simon Willison's Fable 5 agent test as a secure sandbox — yawnxyz · 2026-08-24