How to Fix ‘Trying to Connect’ and Saving Errors in Google Docs

Working on a document in Google Docs only to see the status indicator flash “Trying to connect…” or “Saving…” indefinitely is a disruptive issue that halts real-time collaboration. When this happens, recent edits cannot synchronise with Google Drive’s cloud storage, and attempting to refresh the browser tab risks losing unsaved paragraphs.

This synchronisation failure occurs when local WebSocket connections to Google’s real-time document servers stall, browser caching partitions desynchronise, the Google Docs Offline Chrome extension corrupts local IndexedDB records, or network security appliances intercept persistent TLS streams.

Failure Point	Underlying Cause	Effective Resolution
Stalled Real-Time Socket	Long-lived HTTP/2 or WebSocket stream drops silently	Toggle offline mode or duplicate tab session
Corrupted IndexedDB Storage	Local browser storage containing offline delta edits conflicts with cloud state	Clear site data for docs.google.com
Faulty Chrome Offline Extension	Extension fails to negotiate local synchronization tokens	Disable and re-enable Google Docs Offline extension
DNS / Network Firewall Drops	Proxy server breaks persistent connections to *.docs.google.com	Flush DNS and switch network adapters

Method 1: Preserve Unsaved Edits Before Troubleshooting

Never close or refresh a Google Docs tab immediately while it displays “Trying to connect”. Taking a snapshot of your local document state ensures no content is lost if the web session terminates unexpectedly.

1. Press Ctrl + A (or Cmd + A on macOS) inside the document body to select all text.
2. Press Ctrl + C (or Cmd + C) to copy the text to your operating system clipboard.
3. Open a local text editor such as Notepad on Windows or TextEdit on macOS and paste the contents as a provisional backup.
4. Alternatively, navigate to File > Download > Plain Text (.txt) or PDF Document (.pdf). In many cases, Chrome’s local DOM can compile the export even while background cloud synchronisation is paused.

Method 2: Verify and Reset Google Docs Offline Mode

The official Google Docs Offline extension allows editing without an active internet connection. If its internal database becomes corrupt, it blocks online writes.

1. Open a new browser tab and navigate to https://drive.google.com/drive/settings.
2. In the General settings tab, locate the Offline section.
3. If the checkbox labelled “Create, open and edit your recent Google Docs, Sheets, and Slides files on this device while offline” is checked, uncheck it temporarily.
4. Wait 10 seconds, then re-check the option to force Google Drive to rebuild its local storage schema.
5. Return to your original document tab and check if the status switches to Saved to Drive.

Method 3: Clear Site Data and IndexedDB for Google Docs

Web applications like Google Docs store operational state in Chrome’s local IndexedDB. Purging stale site data for the Google Docs origin clears conflicting synchronisation locks.

1. While viewing the unresponsive document, press F12 (or right-click anywhere and select Inspect) to open Chrome Developer Tools.
2. Click the Application tab along the top toolbar of DevTools (click the double right arrow >> if hidden).
3. In the left sidebar, click Storage.
4. Ensure the checkboxes for IndexedDB, Local storage, and Cache storage are ticked.
5. Click the Clear site data button.
6. Close Developer Tools and reload the page.

Method 4: Test in Incognito Mode to Isolate Third-Party Extensions

Grammar checkers, privacy blockers, and ad-filtering extensions frequently intercept real-time XMLHttpRequest and WebSocket payloads utilised by Google Workspace.

1. Press Ctrl + Shift + N (or Cmd + Shift + N on Mac) to launch an Incognito window.
2. Sign in to your Google Account and open the affected Google Doc.
3. Type several test characters and observe the upper status indicator.
4. If the status immediately reports Saved to Drive, an installed browser extension is interfering.
5. Type chrome://extensions in your address bar, disable your extensions, and re-enable them sequentially to identify the offending plugin.

Method 5: Flush DNS and Reset Network Stack

If multiple Google services (including Drive and Sheets) exhibit synchronisation lag, your local DNS cache may be routing requests to an unresponsive Google edge node.

1. On Windows 11, search for cmd, right-click Command Prompt, and select Run as administrator.
2. Execute the following commands sequentially:
   ipconfig /flushdns
netsh winsock reset
3. On macOS, open Terminal and run:
   sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
4. Restart your browser and re-establish your Google Docs session.

Preventing Real-Time Synchronisation Drops

To maintain stable synchronisation during prolonged writing sessions, avoid keeping dozens of background Google Docs tabs open simultaneously, as Chrome’s Memory Saver may discard background socket pools. If you regularly work on unstable connections, ensure the Google Docs Offline extension is enabled and verified beforehand.