{"version":"2.1.227","anchor":"six-known-api-error-messages-are-reported-verbatim-in-teleme","canonical_anchor":"six-known-api-error-messages-are-reported-verbatim-in-teleme","heading":"Six known API error messages are reported verbatim in telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/six-known-api-error-messages-are-reported-verbatim-in-teleme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Six known API error messages are reported verbatim in telemetry\n\nSix known API errors, including expired tokens, keep their real text in error reports.\n\n**What**\n\nError telemetry usually replaces the server's message with a generic type-and-status string. A fixed allowlist now exempts six messages, including expired OAuth tokens and oversize requests, so those failures stay distinguishable in aggregate.\n\n**Evidence**\n\n`\"OAuth access token has expired. Re-authenticate to continue.\"`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}