{"version":"2.1.267","anchor":"credential-storage-backend-telemetry-now-distinguishes-fallb","canonical_anchor":"credential-storage-backend-telemetry-now-distinguishes-fallb","heading":"Credential-storage backend telemetry now distinguishes fallback chains","tier":"internal","area":"Credentials","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/credential-storage-backend-telemetry-now-distinguishes-fallb","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Credential-storage backend telemetry now distinguishes fallback chains\n\nCredential storage telemetry now reports which backend or fallback chain was actually used\n\n**What**\n\nTelemetry sent when OAuth login tokens are saved (or fail to save) now tags the storage backend more precisely. It recognizes `keychain`, `plaintext`, and `windows-credman`, as well as composite fallback chains like \"`<x>-with-<y>-fallback`\", and reports anything else as `other`.\n\n**Why**\n\nThis gives more detail on which credential storage method was actually used, including cases where the system fell back from one backend to another, which helps diagnose storage issues across different platforms.\n\n- Area: Credentials\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}