When you collaborate in a Word document with multiple co-authors, real-time sync can pause if one person loses their internet connection or closes the file. This happens because Word’s co-authoring engine waits for the offline user to reconnect before it continues syncing changes from other editors. The result is a frozen sync indicator and delayed updates for everyone still editing. This article explains why Word pauses sync when a co-author goes offline and provides a step-by-step fix to restore real-time collaboration. You will also learn how to prevent this issue in shared documents.
Key Takeaways: Restoring Real-Time Sync After a Co-author Disconnects
- File > Info > Manage Document > Recover Unsaved Documents: Restores the most recent synced version when the current file is stuck in a paused state.
- Save As > Save a Copy: Creates a fresh file that reconnects to the co-authoring service and resumes live sync with remaining editors.
- Co-authoring notification bar (yellow banner): Shows the name of the offline user and a “Try Again” button to force a sync retry.
Why Word Pauses Sync When a Co-author Goes Offline
Word uses a server-based conflict resolution model for real-time co-authoring. When you edit a document stored on OneDrive or SharePoint, Word sends each change to the server. The server then distributes those changes to all active co-authors. If one co-author disconnects — by closing the file, losing Wi-Fi, or experiencing a timeout — the server marks that user’s session as pending. Word on your machine then pauses sync for all users because the server cannot guarantee that the offline user’s local changes have been merged. This is a safety mechanism to prevent data loss or duplicate edits.
The pause affects all co-authors still online. You will see a yellow banner at the top of the document that says “Syncing changes with [offline user name]” or “Waiting for [offline user name].” The sync icon in the status bar stops spinning and shows a checkmark or a warning triangle. Real-time cursor positions and edits from other online users freeze until the offline user reconnects or the server times out their session. The default timeout period is about 10 to 15 minutes, but this can feel much longer during active collaboration.
Steps to Force Resume Sync After a Co-author Disconnects
The following methods force Word to resume syncing with remaining co-authors without waiting for the offline user. Try Method 1 first because it is the fastest and requires no file changes.
Method 1: Use the Co-authoring Notification Bar
- Look for the yellow notification bar
Check the area directly below the ribbon. If sync is paused, Word displays a yellow banner with the offline user’s name and a “Try Again” button. Click the button. - Wait for the sync retry
Word attempts to reconnect to the server and resume syncing. If the offline user has not reconnected, the banner reappears after a few seconds. Repeat this step up to three times. If it fails, proceed to Method 2.
Method 2: Save a Copy to Force a Fresh Sync Session
- Go to File > Save As
Select the same OneDrive or SharePoint folder where the original document is stored. Name the copy something like “DocumentName_v2.docx.” Click Save. - Close the original document
Close the paused document tab without saving. Open the new copy from the same folder. Word creates a new co-authoring session. Only users who have the new copy open will sync in real time. - Share the new copy with co-authors
Click the Share button in the upper-right corner and send the link to the other online users. Ask them to close the original document and open the copy. Sync resumes immediately for all editors of the new file.
Method 3: Force the Offline User Out of the Session
- Open the document in a web browser
Go to the OneDrive or SharePoint site where the document is stored. Right-click the file and select Open in Word for the web. - Check the co-authoring panel
In Word for the web, click the ribbon tab Review > Co-authoring. A panel lists all current editors. Find the offline user’s name and note whether their status shows “Offline.” - Ask the offline user to close the file
Contact the offline user via chat or email and ask them to close the document in their desktop Word app. Once they close it, the server removes their session. Sync resumes for remaining editors within 30 seconds.
If Sync Remains Stuck After the Main Fix
Word Still Shows “Waiting for User” After All Methods
If the yellow banner persists after trying all three methods, the server may have a stale session lock. Close the document on your machine. Open OneDrive or SharePoint in a browser, right-click the file, and select Version History. Restore the most recent version that was saved before the pause began. Open that restored version in Word. This bypasses the locked session entirely.
Co-authors Cannot Open the New Copy
When you use Method 2, co-authors must have edit permissions for the new file. If they receive an access denied error, go to the folder in OneDrive or SharePoint, select the new file, and click Share. Add each co-author by email and assign Can Edit permissions. After they accept the invitation, they can open the file and sync resumes.
Real-Time Sync Is Slow Even After Resuming
If sync resumes but edits appear with a 10-second or longer delay, the document may contain large images or embedded objects that increase file size. Reduce file size by compressing images: select any image, go to Picture Format > Compress Pictures, choose Email (96 ppi), and apply to all images. Then save and re-share the document.
Desktop Word vs Word for the Web: Sync Behavior When a Co-author Disconnects
| Item | Desktop Word | Word for the Web |
|---|---|---|
| Sync pause notification | Yellow banner with “Try Again” button | No banner; sync icon turns gray |
| Auto-resume after timeout | 10-15 minutes if offline user does not reconnect | 5 minutes; session is dropped faster |
| Ability to force remove offline user | No direct option; use web method | No direct option; offline user must close file |
| Save a copy workaround | Works; new file creates fresh session | Not needed; web resyncs faster automatically |
Word for the web handles offline co-authors more aggressively by dropping their session after five minutes. Desktop Word waits longer, which is why the pause feels more persistent in the desktop app. If you collaborate frequently, consider using Word for the web for sessions where users have unstable connections.
You now know why Word pauses real-time sync when a co-author goes offline and how to force resume it using the notification bar, saving a copy, or removing the offline user. For future sessions, ask all co-authors to keep Word updated to version 2306 or later, as Microsoft improved session timeout handling in that release. As an advanced tip, enable AutoSave in File > Options > Save and set the AutoSave interval to one minute so that even if sync pauses, your local changes are saved to the server every 60 seconds.