{"version":"2.1.304","anchor":"grove-config-cache-refreshed-on-transient-fetch-errors","canonical_anchor":"grove-config-cache-refreshed-on-transient-fetch-errors","heading":"A server-fetched setting is not refetched over and over after a temporary error","tier":"internal","area":"Configuration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/grove-config-cache-refreshed-on-transient-fetch-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### A server-fetched setting is not refetched over and over after a temporary error\n\nWhen fetching a cached configuration fails with a temporary error, Claude Code now marks its saved copy as fresh again\n\n**What**\n\nClaude Code fetches a configuration from the server and keeps a saved copy. Before, if the fetch failed, it gave up silently and the saved copy stayed out of date. Now, when the fetch fails with any error other than 401 (not authorised) and a saved copy exists, Claude Code refreshes the saved copy's timestamp so it counts as up to date.\n\n**Why**\n\nThis stops Claude Code from trying to fetch the configuration again and again while the server is having trouble.\n\n- Area: Configuration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}