Retry Policy

Talonic retries failed webhook deliveries with exponential backoff: 1 minute, 5 minutes, 30 minutes, and 4 hours before marking as failed.

If your endpoint returns a non-2xx status code or times out (30s), Talonic retries with exponential backoff:

After 4 failed attempts, the delivery is marked as failed. You can check delivery status and replay events from the dashboard.

Most integrations rely on the default retry schedule and only intervene when a delivery reaches the failed state. A typical debugging workflow is to check the delivery history in the dashboard, identify the HTTP status or timeout that caused the failure, then fix the endpoint and replay the event.

Your endpoint must return a 2xx status code within 30 seconds to be considered successful. Non-2xx responses (including 3xx redirects) and timeouts trigger retries. The X-Talonic-Delivery-Id header remains the same across retries, so use it for idempotent processing on your end.

Pair retry awareness with [Signature Verification](webhook-security) to reject spoofed payloads early. Note that the total retry window spans approximately 4.5 hours from the initial attempt — if your endpoint is down longer than that, use the dashboard replay feature to re-send missed events.