{"version":"2.1.290","anchor":"new-telemetry-fields-and-reason-names","canonical_anchor":"new-telemetry-fields-and-reason-names","heading":"More detail in usage reports, and suspended connections are retried","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-telemetry-fields-and-reason-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### More detail in usage reports, and suspended connections are retried\n\nUsage reports gain several new details, and a suspended stop is now retried like a lost connection\n\n**Unclear.** It is not clear whether the elapsed-time reminder is something a user sees or whether it is switched on.\n\n**What**\n\nClaude Code sends usage reports (telemetry, the background data about how the app is running). These now carry more information:\n\n- Settings writes: whether settings were attempted and whether existing settings could not be read.\n\n- Denials: whether a message was hidden when an action was denied.\n\n- Session details: a device-binding posture value.\n\n- Host details: the host interface version and its minimum version.\n\n- New reason names for an elapsed-time reminder and for carrying a task list forward.\n\n- Model switching and other reports record a few extra fields.\n\nOne change affects behaviour as well as reporting. A stop marked as suspended is now treated as worth retrying, the same way a lost connection already was.\n\n**Why**\n\nThe new names point at an elapsed-time reminder and at reporting how a device is bound to a session.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}