<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Idempotency on Fondsites</title><link>https://fondsites.com/tags/idempotency/</link><description>Recent content in Idempotency on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 13:43:57 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/idempotency/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI Agent Retries and Idempotency: Making Repeated Actions Safe</title><link>https://fondsites.com/ai-agents/guidebooks/agent-retries-idempotency/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/ai-agents/guidebooks/agent-retries-idempotency/</guid><description>&lt;p&gt;AI agent failures are not always dramatic. Sometimes the agent simply tries again. A search times out, so it searches again. A ticket update returns an ambiguous response, so it posts the note again. A queue worker restarts halfway through a task and repeats the last tool call. A human reviewer approves a prepared action, but the approval callback is delayed, so the orchestration layer resubmits the same request. In a pure reading workflow, repetition is usually harmless. In a system that sends messages, changes records, moves files, opens pull requests, creates invoices, or modifies customer state, repetition becomes one of the ordinary ways delegated work creates mess.&lt;/p&gt;</description></item></channel></rss>