When exiting my very old survival world, I get an error message that says “Local save successful but cloud sync failed due to quota. Free cloud space by deleting worlds from the settings menu.” This message does not appear when exiting different worlds. When I go to settings > storage to delete worlds, my only option is to Sync Old Worlds. Syncing these worlds does not clear them from the list, and I cannot select them for deletion, my only options are convert or cancel. The delete button at the bottom, which only appears when I have Multiselect enabled, is grayed out and cannot be selected.
Linked issues
is duplicated by 10
Attachments
Comments 41
The delete button doesn’t even exist without Multiselect enabled. There isn’t a button to click. I’ll try enabling/disabling it and see if there’s any change when I am home.
I should add that I only get the cloud sync error when I'm exiting my ~600Mb, forever world. Any other world works fine and syncs without issue.
Having the same problem! My forever survival world shows 1.2GB and I keep a backup but my other like 5 worlds are all under 20MB. This issue came with the Spring to Life Update.
I have ONE world that is 279mb, gradually overtime my saved data for Minecraft on Xbox will reach 1.6gb or higher and begin to encounter cloud sync failed quota issues, until I upload the world to a realm, delete it locally, and redownload it and it correctly puts my saved data back to below 500mb, this needs fixed!
Issue still persists in Xbox Series X. This all started after an update in mid May. Mojang should make a way to easily export your worlds for backups.
I tried realms, but it gives says “unknown error” once the upload completes.
Small update: I've been in contact with Minecraft support for some time now. The first two thirds of the email chain are just basic troubleshooting advice (all of which I had already tried), but eventually the issue was escalated to Camilla, who recognized the issue and said this,
“Now, it looks like you're actually encountering a known issue which is affecting some players. The development team is currently working on a resolution that should mitigate the issue as soon as possible.”
Whether this is just a cookie cutter response, I cannot tell. I followed up (and had already listed multiple times in previous responses) by asking if she could confirm whether the dev team is aware of this bug report, or if the bug report that @G Real shared above (MCPE-197900) is the same issue, since that one had been resolved on the preview edition.
Fingers crossed!
Got a response already!
Camilla wrote,
“Thank you for getting back to us. I see you were able to find some bug reports regarding this issue - thanks for staying proactive while we shared information about the issue you're facing.
At the time, we cannot confirm that your case is linked to a specific bug in the Minecraft Bug Tracker, as they are best handled by the game developers.
But what we can confirm is that the team is aware and working on improvements, though we don’t have a timeline just yet.”
That is good enough for me, confirmation that at least someone on the dev team is aware of this issue! Thanks Camilla!
Remember guys we still haven't gotten the 1.21.100 update which the original patch note for this issue was listed in. It wont be until later in the year at the earliest.
@Levi Klopfenstein I did open a support ticket back in May and had the same thing happened, it is not unusual that they won't ever confirm anything more they to say something along the lines of ‘they acknowledge, do not have an estimated date or time as to when the fix for the Cloud Sync Failed issue will be released to players. They did assure, however, that the development team is aware of what is occurring and indeed are working on a fix.’ Like @Shane Cardwell mentioned we are waiting for this to be hopefully addressed in 1.21.100 (fingers crossed)
Turn off multi select to delete, usually intentional to not wipe out important worlds. Thats what worked for me.