{"version":"2.1.219","anchor":"fast-mode-disabled-reason-on-turn-completion-telemetry","canonical_anchor":"fast-mode-disabled-reason-on-turn-completion-telemetry","heading":"fast_mode_disabled_reason on turn-completion telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/fast-mode-disabled-reason-on-turn-completion-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### `fast_mode_disabled_reason` on turn-completion telemetry\n\nTurn logs now record why fast mode was skipped, such as env setting or model not allowed.\n\n**What**\n\nTurn-completion events now report why fast mode was not used, alongside the existing state field.\n\n**Details**\n\n- New `fast_mode_disabled_reason` sits next to `fast_mode_state` and is populated from the fast-mode eligibility check.\n- Values include `not_first_party`, `disabled_by_env`, `model_not_allowed`, `sdk_opt_in_required`, `pending` and `unknown`.\n- Present at 18 sites in this build; did not exist in the previous one.\n\n**Evidence**\n\n`fast_mode_disabled_reason`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}