{"version":"2.1.223","anchor":"oauth-refresh-telemetry-gained-a-context-tag","canonical_anchor":"oauth-refresh-telemetry-gained-a-context-tag","heading":"OAuth refresh telemetry gained a context tag","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/oauth-refresh-telemetry-gained-a-context-tag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### OAuth refresh telemetry gained a context tag\n\nLogin token refresh failures are now labelled with the action that triggered them.\n\n**What**\n\nToken refresh failures can now be attributed to the flow that triggered them, and failures with a known context no longer emit the generic failure status.\n\n**Details**\n\n- `tengu_oauth_token_refresh_failure` includes a `context` property when the refresh was made on behalf of a named flow.\n- Plugin scope expansion passes `telemetryContext: \"plugins_scope_expansion\"`.\n- The generic \"oauth_refresh_request_failed\" status is only recorded when no context is present.\n\n**Evidence**\n\n`tengu_oauth_token_refresh_failure`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}