What is Retry with Backoff?

Repeating a failed transient operation after progressively longer delays, usually with randomized jitter and a strict retry limit.

Why does Retry with Backoff matter?

Immediate synchronized retries can worsen an outage, consume rate limits, and duplicate side effects.

Retry a provider timeout after bounded exponential delays, honor server retry guidance, and reuse an idempotency key for any write.

Do not retry permanent validation or permission errors, and do not retry non-idempotent operations without a duplication strategy.

No lesson links to this term yet. Search the course catalog for it.

IdempotencyThe property that repeating the same operation with the same identity does not create additional side effects beyond the first successful…
Rate LimitA policy that caps requests, tokens, concurrent work, or another resource within a defined time or capacity window.
Circuit BreakerA reliability control that temporarily stops calls to a dependency after failures cross a threshold, then probes whether the dependency…
BackpressureA flow-control mechanism that slows or rejects upstream work when a downstream component cannot process it safely at the current rate.
Cost per Successful TaskTotal system cost divided by the number of tasks that satisfy a defined success criterion, including retries, failed runs, tool use, and…
Deadline PropagationPassing the remaining end-to-end time budget to downstream calls so each dependency knows how long the original request can still usefully…
Flaky TestA test that can pass and fail across equivalent runs without a relevant change to the code or intended test environment.
Retry BudgetA bound on retry traffic, usually expressed relative to original requests or over a time window, that prevents retries from consuming…