{"version":"2.1.246","anchor":"telemetry-exporter-flushes-before-shutdown","canonical_anchor":"telemetry-exporter-flushes-before-shutdown","heading":"Telemetry exporter flushes before shutdown","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/telemetry-exporter-flushes-before-shutdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Telemetry exporter flushes before shutdown\n\nPending telemetry is flushed on exit instead of being dropped.\n\n**What**\n\nPending first-party events now get a final flush on exit instead of being dropped. The exporter is held on the host, and shutdown starts the flush and waits for it alongside the telemetry provider's own shutdown.\n\n**Details**\n\n- The exporter also gained token-refresh bookkeeping: which credential a refresh was attempted for, the in-flight refresh, and a retry time for workload identity minting.\n- Two timeouts are now configurable, one for the OAuth refresh and one for waiting on the credential helper process.\n- Applies whenever first-party event logging is enabled.\n\n**Evidence**\n\n`signalFinalFlush`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}