Webhook Retries

Overview

There might be times when a notification can’t be delivered to your listener endpoint, for example if your endpoint is offline. If delivery fails, Branch automatically schedules delivery attempts according to a Branch-configured formula.

Non-Retryable Errors

If your system makes a request to trigger a webhook in the sandbox, and Branch responds with a 400 Bad Request or 422 Unprocessable Content, the webhook will not be automatically retried. Correct the request payload before attempting to retrigger the webhook.

Retry Scheduling Formula

As currently configured, failures will retry after:

• First failure: 30 seconds
• Second failure: 60 seconds
• Third failure: 5 minutes
• Fourth failure: 30 minutes
• Fifth+ failure: every 60 minutes, continuing for 7 days

Idempotency

The webhook that Branch sends you always includes a UUID event_id token that you can use as an idempotency key to deduplicate your received webhooks. This event_id will remain the same in every redelivery attempt of the event. See Webhook Event Data Decryption for an example of event_id in an event.