Webhook retries and delivery history

Webhook delivery is backed by a persisted event, request body, and delivery record. Background upload can continue when connectivity returns.

Updated 2026-11-118 min readPlain Markdown

Successful delivery

Any HTTP status from 200 through 299 marks the delivery as succeeded. Veura records the response status, keeps up to 4 KB of response text for diagnostics, and removes the persisted upload body after success.

Retryable failures

  • Connectivity and transport errors without an HTTP status.
  • HTTP 408 Request Timeout.
  • HTTP 425 Too Early.
  • HTTP 429 Too Many Requests.
  • HTTP 500 through 599 server errors.

The base delay starts at 30 seconds and doubles by attempt, capped at six hours. Veura adds up to 20 percent jitter. A valid Retry-After value is respected within the same delay bounds.

Retry limits

LimitBehavior
Maximum attempts12 upload attempts
Maximum age7 days from delivery creation
Maximum delay6 hours between attempts
Minimum delay30 seconds

When an attempt or age limit is reached, the delivery becomes permanently failed. You can open Delivery History and choose Retry to place it back into the pending queue.

Permanent failures and pauses

  • Most 4xx responses are permanent and are not retried automatically.
  • HTTP 401 or 403 pauses the endpoint and marks the delivery as failed because authentication needs attention.
  • Redirect responses are not followed and do not count as success.
  • A missing persisted event or request body produces a permanent failure.
  • Changing an endpoint filter cancels queued deliveries that the new filter excludes.

Design the receiver for retries

Retries keep the same X-Veura-Event-ID and exact saved body. Use the event ID as an idempotency key so a repeated upload cannot create a duplicate task, message, or database row. The timestamp and signature may change on a later attempt.

Read delivery history

Each saved endpoint exposes Delivery History with Pending, Sending, Waiting to Retry, Delivered, Failed, or Cancelled states. Entries show the event ID, attempt count, HTTP status when available, and the latest diagnostic message.