The plain-English version
Increasing or otherwise controlling the delay between repeated attempts after a failure.
Why it matters
It can prevent immediate retries from amplifying an overloaded dependency.
Let’s make it click
A worker retries a temporary network failure with increasing delays and a maximum attempt count.
Vibe Bro’s heads-up
Classify failures before retrying. If an attempt may already have taken effect, use idempotency or another duplicate-effect protection; do not retry invalid input indefinitely.
The docs behind it
Documentation links checked .
Editorial review · October 28, 2026
Corrected: Safe retry does not require every operation to be intrinsically idempotent: known-before-effect failures can be retried, while ambiguous outcomes require duplicate-effect protection.