{"version":"2.1.319","anchor":"phase-clock-for-uploads-and-telemetry-spans","canonical_anchor":"phase-clock-for-uploads-and-telemetry-spans","heading":"Timing measurements added around uploads and telemetry","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/phase-clock-for-uploads-and-telemetry-spans","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Timing measurements added around uploads and telemetry\n\nClaude Code can now time how long uploads and telemetry flushing take, though this does nothing unless timing is switched on\n\n**What**\n\nClaude Code can now time parts of its own work and sort that time into labelled phases. Two of the phases are \"uploads\" and \"telemetry\", and there are also startup phases. Two things are timed under \"uploads\":\n\n- sending upload requests\n\n- flushing stored stream events\n\nThe timing only runs when a timing clock has been set up. Otherwise it does nothing.\n\n**Why**\n\nThis is internal profiling of where time goes. It has no direct effect on what you see or do.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}