# Webhook Retries

A webhook delivery is considered successful as soon as your endpoint returns an HTTP `2xx` (e.g. `200`) response. A delivery is considered failed and eligible for retry when:

- The response status code is non-`2xx`.
- The request times out (your endpoint does not respond within the configured timeout).
- A connection error occurs (DNS failure, connection refused, or TLS error).

Failed deliveries are retried automatically using exponential backoff:

- **Max attempts:** up to 10 retry attempts.
- **Backoff intervals (minutes):** 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, with a small random jitter added to each interval.
- After 10 failed attempts, no further retries are made and the delivery is marked as failed.

For webhooks whose `delivery_details` include `x_auth_token_credentials`, MeasureOne fetches a fresh authorization token from your token endpoint before **every** attempt. Previously fetched tokens are not reused across retries (they may have expired). If fetching the token fails, that attempt is counted as a failed delivery and follows the same backoff and retry logic.