For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
DashboardGet an API key
Get StartedEventsToolsChangelog
Get StartedEventsToolsChangelog
  • Welcome
    • Overview
    • Quickstart
  • Concepts
    • Event envelope
    • Receiving webhooks
    • Signature verification
    • Retries and backoff
    • Testing
LogoLogo
DashboardGet an API key
Concepts

Retries and backoff

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Signature verification

Next

Testing

Built with

Pivotal retries failed deliveries for 24 hours with exponential backoff. After the final retry, the endpoint is marked unhealthy and we email the workspace owner. The full delivery log lives in the dashboard with one-click replay.

WHAT COUNTS AS SUCCESS
  • Any 2xx response inside the 10-second window.
WHAT COUNTS AS FAILURE
  • Non-2xx response (4xx and 5xx alike).
  • Connection refused, DNS failure, TLS handshake failure.
  • Timeout: no response inside 10 seconds.
RETRY SCHEDULE
AttemptDelay after previous
1immediate
25 seconds
35 minutes
430 minutes
52 hours
65 hours
710 hours
824 hours from first attempt — final
WHEN DELIVERY GIVES UP

After attempt 8, Pivotal:

  1. Marks the delivery as failed in the dashboard.
  2. Increments the endpoint’s failure counter.
  3. Disables the endpoint if it has crossed 100 consecutive failures.
  4. Emails the workspace owner with a link to the delivery log.

You can re-fire any past delivery from the dashboard — payload and headers are identical to the original. The Svix SDK treats replays as new deliveries with the same event.id, so your idempotent handler keeps you safe.