{"version":"2.1.281","anchor":"spinner-tolerates-malformed-api-retry-status-objects","canonical_anchor":"spinner-tolerates-malformed-api-retry-status-objects","heading":"Spinner tolerates malformed API retry status objects","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/spinner-tolerates-malformed-api-retry-status-objects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Spinner tolerates malformed API retry status objects\n\nThe spinner no longer breaks on a malformed API retry status and shows \"API error\" or skips it instead\n\n**What**\n\nWhile Claude Code waits and retries a request to the API, the service that runs the model, the spinner (the animated waiting indicator) can show retry details. It now checks those details before drawing them. If it cannot draw one, it either skips it or replaces its error with a stand-in message reading \"API error\". It also reports a `MalformedRetryStatusError` that names what was wrong, and its log message says the session is unaffected.\n\n**Why**\n\nBadly formed retry information no longer trips up the waiting display, and the session carries on."}