You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
API ErrorsArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
The logic that decides whether an API error should be retried rather than treated as fatal now treats any error in the 4xx range as retryable, except for 401 (unauthorized), 403 (forbidden), and 429 (rate limited). Previously only the specific codes 400, 404, and 405 were treated this way. The check also now reads the error's text body using a different helper function.
Why
This means more kinds of client-side errors from the API will be retried automatically instead of immediately surfacing as a failure, which should reduce the number of errors that interrupt a session unnecessarily.
