{"version":"2.1.242","anchor":"a-stale-on-disk-auto-mode-killswitch-no-longer-keeps-auto-mo","canonical_anchor":"a-stale-on-disk-auto-mode-killswitch-no-longer-keeps-auto-mo","heading":"A stale on-disk auto-mode killswitch no longer keeps auto mode off","tier":"notice","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-stale-on-disk-auto-mode-killswitch-no-longer-keeps-auto-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A stale on-disk auto-mode killswitch no longer keeps auto mode off\n\nA stale local file can no longer keep auto mode switched off; startup re-checks the server.\n\n**What**\n\nIf the cached auto mode configuration said disabled and that value came from disk rather than a live override or server payload, it is now read back as enabled, and startup re-checks the killswitch against the remote config service before deciding. A stale local file can no longer keep auto mode switched off indefinitely.\n\n**Details**\n\n- Two new startup awaits: initialising the remote config before mode selection, and the killswitch recheck itself, timed as `growthbook_killswitch_recheck_ms`.\n- Only values sourced from an explicit override or a server payload are still honoured as disabling.\n\n**Evidence**\n\n`growthbook_killswitch_recheck_ms`\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}