{"version":"2.1.265","anchor":"turn-result-wall-clock-timing-fields-now-gated-to-the-matchi","canonical_anchor":"turn-result-wall-clock-timing-fields-now-gated-to-the-matchi","heading":"Turn-result wall-clock timing fields now gated to the matching user message","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/turn-result-wall-clock-timing-fields-now-gated-to-the-matchi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Turn-result wall-clock timing fields now gated to the matching user message\n\nTurn-timing fields in the result event now only appear when they match the current turn's user message\n\n**What**\n\nIn the final `result` event that Claude Code emits at the end of a turn, two wall-clock timing fields, `request_sent_wall_ms` and `first_stream_post_wall_ms`, are now only included when they belong to the same user message that the current turn is actually reporting on. The other send-echo timing fields are still always included as before.\n\n**Why**\n\nPreviously these two timing fields could be attached to a result even when they came from a different user message than the one the result was about, which could make timing data misleading. Restricting them to the matching message keeps the reported timings accurate.\n\n- Area: Telemetry\n- Names: `request_sent_wall_ms`, `first_stream_post_wall_ms`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}