{"version":"2.1.285","anchor":"resuming-a-session-that-ended-at-max-turns-is-classified-as","canonical_anchor":"resuming-a-session-that-ended-at-max-turns-is-classified-as","heading":"A turn that stopped at the turn limit is no longer resumed as interrupted","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/resuming-a-session-that-ended-at-max-turns-is-classified-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### A turn that stopped at the turn limit is no longer resumed as interrupted\n\nOn resume, a turn that stopped at the max-turns limit now counts as complete and is not re-run as if it had been interrupted\n\n**Unclear.** It is not clear exactly what a reader sees differently on resume.\n\n**What**\n\nClaude Code can be given a limit on how many turns (rounds of work) it takes. When you resume a session, Claude Code checks how its last turn ended. A turn that stopped because it hit that limit is now counted as finished at the limit. Before, it was counted as interrupted and could be picked up and run again automatically.\n\n**Why**\n\nResuming a session that stopped at its turn limit no longer re-runs the last turn, which had in fact been stopped on purpose.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}