{"version":"2.1.318","anchor":"resumeinterruption-telemetry-includes-cutoffmidwork","canonical_anchor":"resumeinterruption-telemetry-includes-cutoffmidwork","heading":"Resume tracks whether an interrupted turn was cut off mid-work","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/resumeinterruption-telemetry-includes-cutoffmidwork","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Resume tracks whether an interrupted turn was cut off mid-work\n\nA new cutOffMidWork flag records whether an interrupted turn stopped mid-work, and resume sorts API-error interruptions differently\n\n**What**\n\nWhen a turn is interrupted, for example by a crash or a dropped connection, Claude Code can nudge Claude to carry on when you resume. A turn is one exchange of you asking and Claude answering. That handling changed.\n\n- A new `cutOffMidWork` flag is part of the saved state of an interrupted prompt.\n\n- The diagnostic record for interrupted turns now includes `cutOffMidWork`.\n\n- Turns that ended on an API error are sorted more simply. The `no_request_token` case is now set by a fixed named value. The `other` case applies only when the failed response had no tool call in it. Before, it applied whenever the error was not removed media or a cut-off stream.\n\n**Why**\n\nThis changes the nudge Claude gets after an interrupted turn, so resuming after a crash may pick up differently depending on whether Claude was in the middle of work.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}