Who's building agents that recover from mistakes? Partial failures across systems are the blind spot
djgoel123 · reddit · 2026-11-16
Everyone is building agents that take action; few are building agents that recover from mistakes. The author sketches the scenario of an agent updating customer records across three systems where the third step fails, leaving inconsistent state where blind retries make things worse.
Key questions to answer before granting multi-system write access: which actions are safe to retry, how to detect partial completion, whether actions can be reversed, what to do when reversal is impossible, and who gets notified. Log what actually happened, not just intent. An agent completing 95% of tasks while leaving 5% inconsistent creates heavy operational overhead. He asks whether production teams design recovery workflows up front or bolt them on after failures.
Related event: Who cleans up after failed agents? Recovery layer gains attention(2 posts)→
More from coding & agent
- How are people handling agent versioning, memory, and cross-device sync? — yangyi · 2026-11-16
- Vibe-coded movie seat picker hits 200K users in 24 hours after 3-hour build — itsOmSarraf_ · 2026-11-16
- Proof of Agent hits 1M onchain transactions and 10,000 agents in just 27 days — adamamcbride · 2026-11-16
- Indie dev: Gemini4 Carbon matches 90-95% of Opus 5.5 for coding but is painfully slow — yihui_indie · 2026-11-16
- Running an always-on agent locally: 22 background runs used just 0.41% of quota across 1.51B tokens — Adorable-Cost-3249 · 2026-11-16
- ICL alone may enable substantial continual learning, plot shows agents improve by Month 3 — xennygrimmato_ · 2026-11-16