{"version":"2.1.282","anchor":"new-failure-reason-when-a-folders-starting-snapshot-is-miss","canonical_anchor":"new-failure-reason-when-a-folders-starting-snapshot-is-miss","heading":"Clearer message when a folder's starting snapshot has gone missing","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-failure-reason-when-a-folders-starting-snapshot-is-miss","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Clearer message when a folder's starting snapshot has gone missing\n\nWhen a folder's starting snapshot for the session is missing from this machine, Claude Code now says so in plain words\n\n**Unclear.** What causes the starting snapshot to go missing is not stated.\n\n**What**\n\nWhen Claude Code cannot record the state of a folder, it explains why. It now has a specific message for one case: \"this folder's starting snapshot for the session is gone from this machine's store\". Before, this case fell through to a generic line ending in \"start gone\".\n\n**Why**\n\nIf syncing or uploading a session fails because Claude Code cannot find the saved starting point for a folder, the message now says that directly.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}