{"version":"2.1.283","anchor":"restore-failure-gets-a-new-no-basis-reason-for-uploads-tak","canonical_anchor":"restore-failure-gets-a-new-no-basis-reason-for-uploads-tak","heading":"Clearer message when a restore fails because of when the snapshot was uploaded","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/restore-failure-gets-a-new-no-basis-reason-for-uploads-tak","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Clearer message when a restore fails because of when the snapshot was uploaded\n\nRestoring a snapshot now gives a specific reason when it was uploaded before the earlier environment had any of your files\n\n**Unclear.** Which kinds of session can reach this restore path is not established.\n\n**What**\n\nRestoring a snapshot of your files can now fail with a specific reason. It applies when the upload being restored was made before the earlier environment had taken in any of your files. Claude Code shows one wording to you and a separate one to the model, explaining that a restore cannot build on that upload yet.\n\n**Why**\n\nIn this case you get an exact explanation instead of a vaguer failure.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}