{"version":"2.1.228","anchor":"distinct-telemetry-when-remote-control-token-refresh-runs-ou","canonical_anchor":"distinct-telemetry-when-remote-control-token-refresh-runs-ou","heading":"Distinct telemetry when remote-control token refresh runs out of options","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/distinct-telemetry-when-remote-control-token-refresh-runs-ou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Distinct telemetry when remote-control token refresh runs out of options\n\nRunning out of ways to refresh the remote-control token is now recorded under its own code.\n\n**What**\n\nExhausting the remote-control token refresh chain with neither credential source available is now recorded under its own code before the auth failure is surfaced.\n\n**Evidence**\n\n`chain_exhausted_no_oauth`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}