<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webhooks on FlowChassis.com</title>
    <link>https://flowchassis.com/tags/webhooks/</link>
    <description>Recent content in Webhooks on FlowChassis.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flowchassis.com/tags/webhooks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Webhook Delivery With FlowChassis Backs Off Between Retries and Dead-Letters What Fails</title>
      <link>https://flowchassis.com/webhook-delivery-with-flowchassis-backs-off-between-retries-and-dead-letters-what-fails/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://flowchassis.com/webhook-delivery-with-flowchassis-backs-off-between-retries-and-dead-letters-what-fails/</guid>
      <description>&lt;p&gt;If your product sends webhooks, you&amp;rsquo;ve built a small delivery system whether you meant to or not. Customers&amp;rsquo; endpoints go down, answer slowly, return errors for an hour during their own deploy, or get deleted without anyone telling you. Each event has to get there once, eventually, or end up somewhere a person can see it.&lt;/p&gt;&#xA;&lt;p&gt;The rules are well known. Retry on 5xx and timeouts, waiting longer each time. Stop on a 410 Gone. Sign every request so the receiver can trust it. Send the same delivery ID on every attempt so the receiver can drop a duplicate. And when you give up, put the event in a dead-letter queue instead of losing it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
