{"version":"2.1.318","anchor":"flush-waits-for-oauth-refresh-after-analytics-when-a-conditi","canonical_anchor":"flush-waits-for-oauth-refresh-after-analytics-when-a-conditi","heading":"Usage data can be sent before waiting on a sign-in refresh","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/flush-waits-for-oauth-refresh-after-analytics-when-a-conditi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Usage data can be sent before waiting on a sign-in refresh\n\nUnder some condition, Claude Code now sends pending usage data first and waits for its sign-in refresh afterwards\n\n**What**\n\nWhen Claude Code sends out its pending usage data, it used to wait first for any refresh of your sign-in to finish. Now, when a certain condition holds, it sends the usage data first and waits for the refresh afterwards. Otherwise it keeps the old order.\n\n**Why**\n\nThis changes the order of steps when Claude Code finishes up, such as when it shuts down.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}