{"version":"2.1.302","anchor":"session-resume-can-be-refused","canonical_anchor":"session-resume-can-be-refused","heading":"Resuming a session can now be recorded as refused, not only as failed","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/session-resume-can-be-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Resuming a session can now be recorded as refused, not only as failed\n\nWhen Claude Code declines to resume a past conversation for one specific reason, it now records that as refused instead of as a failed load\n\n**Unclear.** It is not clear what causes Claude Code to refuse a resume.\n\n**What**\n\nResuming a session means reopening an earlier conversation so you can carry on where you left off. Claude Code previously recorded every problem while loading a conversation for resume as a failed load. One specific kind of error is now handled separately. Claude Code records it with a \"refused\" status and passes the error on instead of treating it as an ordinary load failure.\n\n**Why**\n\nThere is now a separate way for a resume to fail. A refused resume is a different outcome from a conversation that simply could not be loaded.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}