---
title: "Webhook and replay errors"
description: "<p>Resolve endpoints, signatures, secrets, cursors, deliveries, replay ranges, and terminal state.</p>\n<h2 id=\"how-it-works\">How it works</h2>\n<p>Resolve endpoints, signatures, secrets, cursors, deliveries, replay ranges"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.messages.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook and replay errors

<p>Resolve endpoints, signatures, secrets, cursors, deliveries, replay ranges, and terminal state.</p>
<h2 id="how-it-works">How it works</h2>
<p>Resolve endpoints, signatures, secrets, cursors, deliveries, replay ranges, and terminal state. Messages.org keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.</p>
<h2 id="set-it-up">Set it up</h2>
<ol>
<li>Read the stable code, HTTP status, request ID, and affected resource.</li>
<li>Classify the response as validation, permission, state, capacity, provider, media, or transient.</li>
<li>Correct permanent failures or retry transient failures with bounded backoff and the original Idempotency-Key.</li>
</ol>
<h2 id="what-to-expect">What to expect</h2>
<ul>
<li>The operation is traceable by stable request and resource identifiers.</li>
<li>Acceptance, provider delivery, and customer interaction remain separate states.</li>
<li>Retries and reordered events do not duplicate the customer action.</li>
</ul>
<blockquote>
<p>[!TIP] Apply retry budgets per resource; never replay an entire failed queue at once.</p>
</blockquote>

Source: https://help.messages.org/errors/webhook-and-replay-errors/index.mdx