Identify connect, read, deadline, and upstream API timeouts, isolate the failing layer with two focused tests, and retry safely without duplicate
API Timeouts: Find the Breakpoint and Retry Safely
An API timeout does not prove that the “model is down.” It means one participant in the chain stopped waiting: the client failed to connect, waited too long for data, exhausted the overall deadline, a proxy closed an idle connection, or the gateway did not receive a response from upstream. Fix only the layer you have confirmed instead of increasing every timeout at once.
Where a request can break
Приложение / SDK
→ DNS и TCP/TLS соединение
When you call another service over HTTP, you are inheriting its worst day. If that dependency slows...
When you call an external API, things go fine until they don't. A network blip, a server restart, a...
When an AI API call fails, the tempting reaction is to switch models or providers. That is often...
Most API bugs are not exotic: a missing field, a wrong status code, a timeout under load, or a...
TL;DR If your OpenAI, Claude, or Gemini API calls are failing with cryptic errors that...
Thirty seconds. That was my timeout. Why? It felt safe. It was not. I watched a batch job die twice....
