{"version":"2.1.247","anchor":"internal-metrics-exporter-gains-401-recovery-redirect-refusa","canonical_anchor":"internal-metrics-exporter-gains-401-recovery-redirect-refusa","heading":"Internal metrics exporter gains 401 recovery, redirect refusal and export telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/internal-metrics-exporter-gains-401-recovery-redirect-refusa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Internal metrics exporter gains 401 recovery, redirect refusal and export telemetry\n\nInternal metrics export now recovers from expired tokens and refuses redirects.\n\n**What**\n\nFor builds that export internal metrics, posts now recover from an expired OAuth token: a 401 re-reads the token and, if unchanged, attempts one refresh per exporter before retrying. Redirects are refused outright. A token-exchange error that previously counted as success when the org setting said metrics were disabled now fails the export.\n\n**Details**\n\n- The refused-redirect behaviour comes from setting the maximum redirects to zero on each post.\n- The swallowed exchange error is now reported as `wif_error`.\n- New telemetry reports the first successful export and de-duplicated failures, including the HTTP status where known.\n- A shutdown-budget timer reports exports still in flight when the process is winding down as a failure.\n- No feature flag; only trust and endpoint checks decide whether this runs.\n\n**Evidence**\n\n`BigQuery metrics export still in flight at the shutdown budget`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}