Source code
Stability
Performance
No retries / backoff on external call
Part of the Error handling & resilience check · fix arrives as a guide
What it is
A call to an external dependency has no retry, or retries immediately with no backoff between attempts.
Why it matters
Without retries a one-second network blip is a user-visible failure. With immediate retries you add load to a service that is already failing, which is how a brief degradation turns into a sustained one.
How to fix it
Retry idempotent operations two or three times with exponential backoff and jitter. Do not retry 4xx responses — they will not succeed — and make non-idempotent operations safe with an idempotency key before retrying them at all.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.