{"version":"2.1.281","anchor":"policy-limits-fetch-retries-after-an-invalid-format-parse-f","canonical_anchor":"policy-limits-fetch-retries-after-an-invalid-format-parse-f","heading":"Policy-limits fetch retries after an invalid-format (parse_failed) response even when retries are otherwise skipped","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/policy-limits-fetch-retries-after-an-invalid-format-parse-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Policy-limits fetch retries after an invalid-format (parse_failed) response even when retries are otherwise skipped\n\nA malformed policy-limits response is now retried even when retries are otherwise switched off, instead of being given up on\n\n**Unclear.** The finding does not say which of `tengu_shimmying_stardust` and `tengu_policy_limits_fetch` sets `skipRetry`.\n\n**What**\n\nClaude Code fetches policy limits from a server. A response that does not match the expected format is now marked with the error code `parse_failed`. The retry and stale-fallback path, which tries again or falls back to older saved data, now runs for `parse_failed` even when `skipRetry` is set.\n\nWhether `skipRetry` is set depends on a server-controlled switch. When that switch is on, a malformed response now triggers another attempt instead of Claude Code giving up.\n\n**Why**\n\nA garbled server response no longer ends the policy-limits fetch where it previously would have.\n\n- Flag `tengu_shimmying_stardust`: Off in both readings (read for one account on one subscription tier against v2.1.281; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release."}