{"version":"2.1.284","anchor":"telemetry-flush-delays-one-exporters-flush-until-pending-wo","canonical_anchor":"telemetry-flush-delays-one-exporters-flush-until-pending-wo","heading":"One telemetry sender waits briefly for pending work before its final flush","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/telemetry-flush-delays-one-exporters-flush-until-pending-wo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### One telemetry sender waits briefly for pending work before its final flush\n\nOn shutdown, one telemetry sender now waits up to half the flush time limit for pending work to finish before sending\n\n**Unclear.** Which telemetry sender this is, and what work it waits for, is not clear.\n\n**What**\n\nWhen Claude Code shuts down, it sends out any usage data (telemetry) it has not sent yet. This is called flushing. One of the senders now waits up to half of the flush time limit for pending work to finish before it flushes. Before, it flushed straight away.\n\n**Why**\n\nThis probably means fewer telemetry records are lost when some are still being produced as Claude Code shuts down.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}