Save not syncing

What to check

Make sure you are signed in, avoid private mode, keep one active game tab, and wait after ending a session before closing the browser.

Multiple devices

If you switch devices quickly, the most recent local browser state may not be the one you expect. Let one session finish before opening another.

Avoid overwrites

Do not repeatedly start new sessions if a save looks wrong. Stop and report the issue with the time, device, and last visible game state.

Related pages

Recovery order

First, stay on the same browser and account. Refresh once. If the run still looks wrong, stop and report it before starting another session. Starting over repeatedly can make it harder to know which state should be restored.

If the problem began after a crash or dead battery, say that. Power loss during a write is one of the most important details for save recovery.

What not to do

Do not use private mode for save testing. Do not clear storage unless you are ready to lose local cached files. Do not open the same account in several game tabs to force a sync.

Signs that sync is working

A clean return to the site session screen after ending a run is a good sign. If the browser closes before that point, the site may need to recover from the last local state it saw. Give recovery a chance before resetting anything.

Step by step save check

Save issues need careful handling because repeated launches can hide the original state. Use this order.

• Stay on the same account.
• Use the same browser where the issue happened.
• Refresh once.
• Do not clear site data.
• Do not start several new sessions.
• Write down whether there was a crash, power loss, tab close, or normal End Game.
• Report the time and last visible state.

Common save mistakes

Switching devices immediately after a crash can make recovery harder. Clearing storage can remove local files. Starting another run can make it unclear which state should be treated as current.

Honest limitations

A browser cannot always recover from power loss during a write, private mode storage wipes, or a device that kills the tab in the background. The site can improve recovery, but the safest path is still a clean session end.

What support needs to recover context

The most useful details are the account, approximate time, device, browser, and whether the session ended normally. If a laptop died, a tab crashed, or the browser showed a white screen before recovery, say that clearly.

If you remember the ante, round, score, or whether the session had just ended, include it. That can help match the report to the stored session history.

When a reset is the wrong move

A reset should be a last resort, not the first fix. If the site still has a chance to recover the previous session, resetting local data can remove useful files. Report first when the run matters.