A sound retry policy needs jitter, caps, idempotency, a read of Retry-After and a budget. Here is each piece, and the storms that follow when one is missing.
A correct retry policy repeats only calls that can safely be repeated, only after errors that can change, with a wait that grows and carries a random part, under a hard limit on tries and on total time, and with a shared budget so that a sick dependency is not buried under its own clients. Each piece guards against a different failure. Leave one out and a ten-second blip can become an hour-long outage, because the retries themselves are traffic. The rest of this page goes through the pieces in the order a request meets them, then the storms you get when they are missing.
Read the full report on AISkills402: https://aiskills402.com/blog/retry-backoff-mistakes?utm_source=devto&utm_medium=social
