{"version":"2.1.248","anchor":"auto-mode-can-be-switched-off-server-side-when-fast-is-on","canonical_anchor":"auto-mode-can-be-switched-off-server-side-when-fast-is-on","heading":"Auto mode can be switched off server-side when \/fast is on","tier":"soon","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/auto-mode-can-be-switched-off-server-side-when-fast-is-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Auto mode can be switched off server-side when \/fast is on\n\nAuto mode can be disabled server-side while \/fast is on, but nothing sets that today.\n\n**What**\n\nA new circuit breaker disables auto mode with the reason \"fast-mode\" when the remote `tengu_auto_mode_config` object sets `disableFastMode` and you have `\/fast` toggled on. There is no local fallback value for `disableFastMode`, so with no server config it is undefined and the breaker never fires. This replaces the old branch that blocked auto mode for providers lacking an opt-in.\n\n**Details**\n\n- The debug output now reports a `disableFastModeBreakerFires` counter.\n\n**Evidence**\n\n`auto mode disabled: tengu_auto_mode_config.disableFastMode with the \/fast toggle on`\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Auto Mode\n- Names: `\/fast`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}