Report

Help us improve this tool

Webhook Retry Schedule Calculator

Model webhook retry delays with base interval, multiplier, jitter, and max delay caps.

O M T

Plan webhook retry backoff before you ship

SaaS platforms retry failed webhook deliveries with exponential backoff, jitter, and a maximum delay cap. Guessing those numbers in a spreadsheet is error-prone. This calculator models each retry attempt using your base delay, multiplier, jitter percentage, and cap so you can see per-attempt waits and total time before the queue gives up.

How the schedule is computed

  1. Attempt 1 waits the initial delay (often 1–5 seconds).
  2. Each later attempt multiplies the previous base delay by your backoff factor (commonly 2×).
  3. Delays never exceed the max delay you set (for example 60 seconds).
  4. Jitter shows a min/max band at ± the percent you enter; production systems pick a random value inside that band to avoid thundering herds.

Pair this with the Webhook Signature Verifier when testing signed callbacks end-to-end.

Frequently Asked Questions

Does this match Stripe or GitHub exactly?

Vendors use proprietary jitter and attempt limits. Use this table as a planning guide, then confirm against the provider’s current documentation.

Why show cumulative “base” time?

Summing uncapped base delays shows worst-case wait if jitter were zero. Real deliveries land between the min and max jitter columns.

Is data sent to the server?

No. All math runs in your browser.