{"version":"2.1.282","anchor":"remote-directory-sync-explains-an-upload-that-could-not-be-r","canonical_anchor":"remote-directory-sync-explains-an-upload-that-could-not-be-r","heading":"Remote sessions explain when an earlier upload could not be read","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/remote-directory-sync-explains-an-upload-that-could-not-be-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Remote sessions explain when an earlier upload could not be read\n\nWhen earlier work cannot be restored in a remote session, Claude Code can now say a later upload could not be read from storage\n\n**What**\n\nIn a remote session (one that runs in a cloud container rather than on your computer), the container can be replaced. When earlier work cannot be restored afterwards, Claude Code gives a reason. A new reason has been added: \"a later upload could not be read from the session's storage\". It joins the existing reasons for refused, git failures, unusable data, being offline and data not stored.\n\n**Why**\n\nIf your earlier work is missing from a remote session, the message now tells you more precisely what went wrong.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}