New event delivery retry strategy

Webhook event retries now use base-2 exponential back-off (10s, 20s, 40s, 80s…), replacing the previous base-10 progression. Initial retries are faster while later attempts remain spaced out.

What's new

maximum_wait_time is an optional parameter configurable per webhook. It sets an upper bound on the total time an event is retried from its first delivery attempt. When this duration is exceeded, the event is marked as failed regardless of remaining retries.

If maximum_wait_time is not set, the existing behaviour is preserved: retries continue until the retry count is exhausted.

What changed

The retry interval progression changed from base-10 to base-2 exponential back-off. The retry sequence is now 10s, 20s, 40s, 80s, and so on.

No migration is required. Existing webhooks continue to work with the new retry timing automatically.