Retries are capped and backed off, and every outbound call times out
grep -rn "fetch(" src/ | grep -vc "signal" # fetches with no abort signalgrep -rnE "retry| retries" src/ | grep -viE "backoff| jitter| max"
Get the free fixes for code AI gets wrong
Each one shows what the AI wrote, what it should have written, and how to check your own app
What is going on
Three layers each retrying three times is 27 requests for one failure. AWS's October 2025 postmortem calls the result "congestive collapse," where engineers throttled traffic by hand. Node's fetch has no useful default timeout, so a hung upstream is a function you pay for by the second.
Where it bit
Not in ours, by luck more than design. It is the retry storm, the one that multiplies, and the most expensive of the five in this group.
The practice
Retry at one layer only, capped exponential backoff with jitter, honor Retry-After. AbortSignal.timeout(5000) on every fetch, statement_timeout on Postgres, explicit maxDuration on functions. A circuit breaker for anything that can go down for an hour.
Get this check as a script you can run tonight

Make your coding agent prove it didn't cheat
Coding agents special-case, skip or edit tests so the check goes green. A five-sentence prompt Anthropic tested took Claude Opus 4 from cheating in 47% of runs to 5%- 3 min read
How to pick who fixes your vibe-coded app
Your app was built fast with AI and now something is wrong. Here is who can fix it, what they should do before they quote, the questions to ask and the red flags to walk away from - 3 min read
What an app check covers
An app check is an engineer reading the app your AI tools wrote, ranking what will break and writing the fix for each problem. Here is every area it covers, how the five days run and what you keep at the end
If this check came back with more than you expected, that is worth a conversation