{"version":"2.1.323","anchor":"rewind-and-continuation-traceparent-and-carried-turn-handli","canonical_anchor":"rewind-and-continuation-traceparent-and-carried-turn-handli","heading":"Resumed and continued sessions keep their tracing link","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rewind-and-continuation-traceparent-and-carried-turn-handli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Resumed and continued sessions keep their tracing link\n\nResumed or continued sessions now carry over the tracing identifier from the last user message\n\n**What**\n\nWhen you resume or continue a session, it now takes over the tracing identifier from the previous user message. A tracing identifier links related requests together in monitoring tools.\n\nAfter compaction, which is when Claude Code shortens a long conversation by summarising it, the set of tools carried on as not allowed is rebuilt from the prompt of the turn that was running.\n\n**Why**\n\nTracing stays linked across compaction and resume.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}