How webhook retries work.

Webhook deliveries are persisted before they enter the queue. Each delivery has its own public identifier, attempt counter and client-safe error state.

Retry schedule

Failures use the configured 3, 10, 30, 60, 360 and 1440 minute backoff. Redirects are not followed. Each attempt uses the endpoint signing secret and signs the exact JSON body with a current timestamp.

An exhausted delivery can be replayed from the console. A replay receives a new delivery identifier and includes the original identifier in `replay_of`, allowing consumers to choose their own deduplication policy.