<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Retries on TaskFused.com</title>
    <link>https://taskfused.com/tags/retries/</link>
    <description>Recent content in Retries on TaskFused.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://taskfused.com/tags/retries/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Client Retries After a Timeout With TaskFused, the Second Request Joins the First</title>
      <link>https://taskfused.com/client-retries-after-a-timeout-with-taskfused-the-second-request-joins-the-first/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://taskfused.com/client-retries-after-a-timeout-with-taskfused-the-second-request-joins-the-first/</guid>
      <description>&lt;p&gt;A phone app sends &amp;ldquo;import my contacts&amp;rdquo; to your server. The import takes twelve seconds, but the app gives up after ten, because that&amp;rsquo;s what its HTTP client does by default. It shows a spinner and sends the request again. Now the server is running two imports of the same contacts into the same account, and the user ends up with every contact twice.&lt;/p&gt;&#xA;&lt;p&gt;Retries like that are normal and mostly good. Networks drop replies, phones switch from Wi-Fi to mobile data, and a client that never retried would leave users stuck. The trouble is a retry that can&amp;rsquo;t tell it&amp;rsquo;s a retry. TaskFused gives the server a way to tell.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
