同步卡住

有时，当您的帐户同步时，仪表板上显示的同步状态会定格在某个百分比（通常在10%）。这说明同步出现了问题，正在停止或暂停同步过程。

确保您正在阅读正确的指南

在我们有多个关于同步问题的解决指南，在继续阅读之前，请确保你正阅读的是为你的问题准备的，要查看同步问题总览，请前往 同步错误。

这些问题略有不同，可能需要不同的步骤，因此我们将它们分成单独的指南。

DO NOT

• Delete your Neos data/database or cache files. Doing this will likely make you lose your unsynced items, and can cause other side effects
• Try to save and sync any more items/worlds. Doing this will add to your sync queue and if your items/worlds are not syncing properly.
• Click "Exit & Save Homes". Doing this will also add to your sync queue.
• Send any objects or voice messages through the Contacts tab. Doing this will also add to your sync queue and will not send until any syncing issues are fixed.
• Change any settings. Doing this will also add to your sync queue and will not save properly until any syncing issues are fixed.
• Reinstall Neos. Doing this does not help syncing issues, as these are stored in a separate location.

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:

1. 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
2. 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.
3. If it is still not moving, then you have a stuck sync!

修复卡住的同步

修复一次正卡住的同步有点挑战性，具体取决于问题所在，因此请务必按照我们的步骤操作。

1. Examine your Log Files
2. The most recent file that shows a stuck sync, should be the one that you examine.
3. Scroll through it looking for issues, If you're unsure try asking on the Discord and somewhere there will be able to identify where the Stuck Sync message is.
4. Once you've located 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 occuring between you and our data storage systems which are a part of the Azure cloud service offerings.

You can follow these steps to try and resolve it:

1. Try restarting Neos, this will re-start the sync and try it again.
2. Try waiting for a while before restarting or trying to sync again.
3. 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 -DeleteUnsyncedCloudRecords option 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:

1. Avoid repeatedly saving the same object multiple times - For example, waiting a longer period of time between saving copies of worlds or avatars.
2. Avoid saving multiple items at once - For example, don't grab and save every single object you see.
3. Break up your saves, save an item...wait 5 minutes... save another item.
4. Try using your Local Home as a Local Backup.
5. Continue posting reports, log files and information on the bug report on our issue tracker
6. Ask in our discord for more information.

Conflicts

If you find a message stating that there is a conflict, you'll need to see Sync Conflict page instead.

Something else?

If you can't find something that matches the above list. Please report it on our issue tracker or in our Discord. In both cases make sure to provide a log file.