You have saved all edits in Notion, yet the sync indicator continues to spin or show a warning icon. This problem often occurs when the Notion client fails to confirm that its local cache matches the server state. The sync indicator persists because Notion has not received an acknowledgment from its cloud servers for one or more pending changes. This article explains the common causes behind a stuck sync indicator and provides clear steps to resolve the issue.
Key Takeaways: Fixing a Stuck Notion Sync Indicator
- Force-quit and relaunch Notion: Clears a stuck client process that may be holding a failed sync request.
- Check your internet connection: A weak or intermittent connection prevents the sync handshake from completing.
- Clear the Notion cache folder: Removes corrupted local data that can block sync acknowledgments.
Why the Notion Sync Indicator Gets Stuck
Notion uses a real-time sync protocol that sends every keystroke and change to its cloud servers. When you edit a page, Notion queues the change locally and immediately attempts to send it to the server. The sync indicator shows a spinning icon while the change is in transit and a checkmark once the server confirms receipt.
The indicator persists when the server acknowledgment never arrives. This can happen for several technical reasons: the local client may have a stale authentication token, the network connection may drop mid-sync, or the Notion desktop app may have a corrupted cache that prevents it from processing the server response. In rare cases, a firewall or VPN can block the WebSocket connection that Notion uses for live sync.
The problem is almost never caused by the actual content of your edits. It is a communication failure between the Notion client and the Notion server. Understanding this root cause helps you apply the correct fix instead of re-saving pages repeatedly.
Steps to Clear a Stuck Sync Indicator
Follow these steps in order. Test the sync indicator after each step to see if the issue is resolved.
- Force-quit and relaunch Notion
On Windows, press Ctrl+Shift+Escape to open Task Manager. Find Notion in the list of processes. Right-click it and select End task. Then open Notion again. On macOS, press Command+Option+Escape, select Notion, and click Force Quit. This clears any temporary sync lock the client may have. - Check your internet connection
Open a web browser and visit a site like google.com. If the site loads slowly or not at all, restart your router or switch to a different network. Notion requires a stable connection to complete the sync handshake. A weak Wi-Fi signal can cause the sync indicator to spin indefinitely. - Sign out and sign back into Notion
Click your profile picture or initials in the top-left corner of the Notion window. Select Settings & Members. In the left sidebar, click My Account. Scroll down and click Log out of this workspace. Close Notion completely, open it again, and sign in. This refreshes your authentication token and forces a new sync session. - Clear the Notion cache
Close Notion completely. On Windows, press Windows+R, type %appdata%\Notion and press Enter. Delete the folder named Cache. On macOS, open Finder, press Command+Shift+G, type ~/Library/Application Support/Notion and press Enter. Delete the folder named Cache. Restart Notion. The app will rebuild the cache from the server, which often resolves sync acknowledgment failures. - Disable VPN or proxy temporarily
If you use a VPN or proxy service, disconnect it and reload Notion. Some VPNs block the WebSocket port (port 443) that Notion uses for live sync. After disabling the VPN, the sync indicator should clear within a few seconds. - Reinstall Notion
If none of the above steps work, uninstall Notion from your computer. Download the latest version from the official Notion website and install it. This replaces any corrupted program files that may be interfering with the sync process.
If Notion Still Shows a Sync Error After Clearing the Indicator
Sync indicator turns red or shows a warning icon
A red sync indicator means Notion has detected a conflict between your local edits and the server version. Open the page that has the conflict. Notion will display a banner at the top of the page with options to Keep your version or Use server version. Select the appropriate option. The sync indicator will return to normal once the conflict is resolved.
Sync indicator spins only on a specific page
If the sync indicator spins only when you open one particular page, that page may contain a large embedded file or a database view that is slow to sync. Try duplicating the page: click the three-dot menu in the top-right corner of the page, select Duplicate, and open the duplicate. If the duplicate syncs normally, the original page had a corrupted sync state. Delete the original page after confirming the duplicate is complete.
Sync indicator persists only in the desktop app but not in the web app
Open the same workspace in a web browser. If the sync indicator shows a checkmark in the browser, the desktop app has a local cache issue. Follow the cache-clearing steps in the previous section. If the problem continues, uninstall and reinstall the desktop app.
Notion Desktop App vs Web App: Sync Behavior Compared
| Item | Desktop App | Web App |
|---|---|---|
| Sync method | WebSocket connection through a local client | WebSocket connection through the browser |
| Cache location | Local file system (%appdata% or ~/Library) | Browser cache (cleared via browser settings) |
| VPN interference | Can block WebSocket port 443 | Also affected, but browser may use alternative protocols |
| Conflict detection | Shows banner on the page | Same banner on the page |
| Recovery after crash | Auto-reloads with previous session | Reload page manually |
After completing the steps in this article, you should see the sync indicator return to a steady checkmark within a few seconds. If the indicator still persists, contact Notion support through the Help & Feedback section in your workspace. As an advanced tip, you can monitor the sync status of a page by pressing Ctrl+Shift+I (Windows) or Command+Option+I (macOS) to open the developer console and looking for WebSocket connection messages.