https://vacua.dev/tags/webhooks/Recent content in Webhooks on Brian FaustHugoen-USMon, 01 Jan 0001 00:00:00 +0000https://vacua.dev/thoughts/a-webhook-delivery-is-not-a-unique-event/Tue, 01 May 2018 00:00:00 +0000https://vacua.dev/thoughts/a-webhook-delivery-is-not-a-unique-event/<p>A subscription callback had already created this local record:</p> <figure class="code-figure"> <div class="code-block" data-copy-code> <button class="copy-code" type="button" aria-label="Copy code">copy</button><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">carrier: external-freight </span></span><span class="line"><span class="cl">subscription_id: sub-demo-17 </span></span><span class="line"><span class="cl">secret: old-secret </span></span><span class="line"><span class="cl">expires_at: 2018-05-08T12:00:00Z</span></span></code></pre></div> </div> </figure> <p>The sender delivered another validation message for <code>sub-demo-17</code>, now with a new secret and expiry. The handler tried to insert a second row. A unique constraint rejected it, so the activation step never ran.</p> <p>The database was right. The handler had mistaken another delivery for another subscription.</p> <h2 id="start-with-the-identity-the-sender-repeated">Start with the identity the sender repeated</h2> <p>A webhook request is evidence that a message was delivered. It is not evidence that this message has never arrived before.</p>