{"version":"2.1.268","anchor":"query-telemetry-can-now-carry-a-resume-reason","canonical_anchor":"query-telemetry-can-now-carry-a-resume-reason","heading":"Query telemetry can now carry a resume_reason","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/query-telemetry-can-now-carry-a-resume-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Query telemetry can now carry a resume_reason\n\nQuery telemetry can now record a resume_reason when a query is triggered by resuming a session\n\n**Unclear.** The finding does not say how or where resume_reason values are used or surfaced beyond internal telemetry.\n\n**What**\n\nWhen Claude Code sends a query, if the event that triggered it carries a `resumeReason` (a note explaining why a session was resumed), that reason is now attached as `resume_reason` in the telemetry data recorded for the query.\n\n**Why**\n\nThis gives internal telemetry more context about why a given query happened, specifically when it follows a session resume, which can help with diagnosing and understanding usage patterns.\n\n- Area: Telemetry\n- Names: `resume_reason`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}