Sometimes, when your account is syncing the sync status as shown on the dashboard will stick at various percentages(10% is common). This indicates that there was a problem while syncing that is halting or pausing the sync process.
Ensure you're reading the right guide
We have multiple guides for Sync related matters, please ensure you are reading the correct one for your problem, for the "Hub" of these see Sync Errors BEFORE you start.
These problems are slightly different and may require differing steps, so we've split them into separate guides.
- Delete your Neos data/database or cache files.
- Try to save and sync any more items/worlds.
- Send any objects or voice messages through the Contacts tab.
- Change any settings.
- Reinstall Neos.
Diagnosing a Stuck Sync
The first step for fixing a Stuck Sync, is to ensure it really is stuck. Sometimes syncing may take a long time or appear stuck but, it's just being slow. Follow these steps to confirm the issue:
- Examine the sync status section of your Dash menu. It is in the top bar of the dash and will usually display "All Synced" in green
- If it says "Syncing" and then a percentage, examine this percentage. See if it changes or increases. Give it a few minutes to double check that its not just being slow.
- If it is still not moving, then you have a stuck sync!
Fixing a Stuck Sync
Fixing a stuck sync, is a little challenging depending on what exactly is wrong so make sure to follow our steps.
First, let's try some steps which are common to many sync issues:
- Try restarting Neos, this will re-start the sync process and can sometimes get it unstuck
- Try disabling any mods, plugins or other modifications you have made to Neos, these may affect syncing.
If you've tried these initial steps then let's move on to discovering exactly what's wrong:
- Examine your Log Files
- The most recent file that shows a stuck sync, should be the one that you examine.
- Scroll through it looking for issues, If you're unsure try asking on the Discord in the #questions-help channel. Send the full log file to whomever is helping you.
- Once you've located or been told about the message that's related to your stuck sync. Follow the section below which most closely matches the issue you're seeing in the log file.
Too Many Requests
If you've found a message that contains something like this:
Fail Reason: Response status code does not indicate success: TooManyRequests (429); Substatus: 3200; ActivityId: ....; Reason: ( code : TooManyRequests message : The request rate is too large. Please retry after sometime. Learn more: http://aka.ms/cosmosdb-error-429,
This error means that there's a rate limit occurring between you and our data storage systems which are a part of the Azure cloud service offerings. This usually happens when items are being saved too quickly or are too large to save temporarily. The issue usually goes away on it's own if you are patient.
However, You can follow these steps to try and resolve it:
- Try restarting Neos, this will re-start the sync and try it again.
- Try waiting for a while before restarting or trying to sync again.
- Try waiting for a quieter time for Neos traffic before syncing. Later at night or earlier in the morning
This may take up to 48 hours to resolve.
If you are impatient, then there are some more items you can try. These WILL CAUSE DATA LOSS:
- Force the Sync to ignore records which are causing it to get stuck. This is done by following the Sync Conflict guide and using the
-DeleteUnsyncedCloudRecordsoption within this guide.
- You can Clear your database.
Avoiding this problem in the future
The Neos team are aware and are investigating this issue, see the bug report on our issue tracker for more information. In the mean time, try these recommendations to potentially reduce the amount of times you see it:
- Avoid repeatedly saving the same object multiple times - For example, waiting a longer period of time between saving copies of worlds or avatars.
- Avoid saving multiple items at once - For example, don't grab and save every single object you see.
- Avoid saving very large objects, for example a very complicated world, instead save portions of the object such as individual rooms or objects separately.
- Break up your saves, save an item...wait 5 minutes... save another item.
- Try using your Local Home as a Local Backup.
- Continue posting reports, log files and information on the bug report on our issue tracker
- Ask in our discord for more information.
We've also seen reports of this occurring with exceptionally large assets. For example very high poly scenes and worlds, anatomically correct research models etc. In these cases these assets contain so much information that they can exceed the rate limiting just by themselves. If this is the case, then please try breaking them up as recommended above.
If you find a message stating that there is a conflict, you'll need to see Sync Conflict page instead.