{"version":"2.1.281","anchor":"telemetry-inherited-withdrawn-field-on-a-request-lifecycle","canonical_anchor":"telemetry-inherited-withdrawn-field-on-a-request-lifecycle","heading":"Telemetry: inherited_withdrawn field on a request lifecycle event","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/telemetry-inherited-withdrawn-field-on-a-request-lifecycle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Telemetry: inherited_withdrawn field on a request lifecycle event\n\nA request lifecycle telemetry event gains an inherited_withdrawn field, sent only when there is an inherited request id\n\n**Unclear.** The finding does not say which requests this event describes or what \"withdrawn\" means for them.\n\n**What**\n\nTelemetry is usage data Claude Code reports back. One telemetry event about a request's lifecycle now includes an `inherited_withdrawn` field. The field is included only when the request has an inherited request id.\n\n**Why**\n\nThis changes what is reported, not how Claude Code behaves.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}