You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.267,
Bug FixesSection of the release
What
The logic that decides whether to log and retry an error after a failed request used to recognize connection_error, server_overload, api_timeout, and rate_limit. It now also recognizes stream_idle_timeout, logging "API {type} after retries" and treating it the same way as those other transient errors.
Why
A connection that goes idle mid-stream is now handled like other temporary network hiccups, so it can be retried instead of surfacing immediately as a failure.
