Pick a retry policy and see when each attempt happens, including the worst case when every attempt times out. Everything runs in your browser; nothing is sent anywhere.

Notes

  • Delay before retry n is base × multiplier^(n−1), capped at the maximum delay.
  • Full jitter waits a random time between zero and that delay, which spreads out clients that failed at the same moment. Equal jitter keeps half the delay fixed and randomises the rest.
  • Latest assumes every attempt runs until its timeout and every wait is the longest possible. This is the number to compare with how long the caller can wait.
  • The defaults match Retry fetch with Exponential Backoff and Jitter, and “Copy fetchWithRetry options” gives you the options object for it. That snippet always uses a multiplier of 2 and full jitter.
  • Switch the units to minutes to plan retries across scheduled runs, as described in Retry, Back Off, Give Up: Handling Unreliable External APIs.