You open Notion after working offline and see a sync error that says conflicts cannot be reconciled. This happens because Notion uses a last-write-wins model for most content types, but certain changes made offline — especially to database properties or page titles — create version branches that the server cannot merge automatically. This article explains why these conflicts occur and provides the exact steps to resolve them, including manual conflict resolution and preventive settings.
Key Takeaways: Fixing Notion Sync Conflicts From Offline Edits
- Notion app notifications panel: Shows pending conflicts that need manual resolution after reconnecting to the internet.
- Conflict resolution dialog: Allows you to pick which version of a page or block to keep when automatic merge fails.
- File > Settings & Members > Notifications > Sync conflicts: Toggle to receive immediate alerts when conflicts occur.
Why Notion Cannot Reconcile Conflicts From Offline Edits
Notion syncs changes in real time when you are online. When you edit a page while offline, the app records those edits locally as a pending change set. Once you reconnect, Notion attempts to apply those changes to the server version. If the same page or database property was also edited by another collaborator during that offline period, the server receives two divergent histories for the same block.
Notion does not support true operational transformation or CRDT-based merging for all content types. Instead, it uses a last-write-wins policy for text blocks and page titles. For database properties — such as select options, relation links, or formula fields — the server cannot decide which value to keep because both edits are equally recent. The system then flags a conflict and stops syncing that page until you manually resolve it.
Common triggers for unreconcilable conflicts include editing a database cell while offline, renaming a page that another user also renamed, and changing the same text block in two different ways. The conflict notification appears in the app and in your email if you have sync alerts enabled.
Steps to Resolve Notion Sync Conflicts Manually
- Open the Notion app and check the notification bell
Click the bell icon in the top-right corner of the sidebar. Look for a notification labeled “Sync conflict” or “Cannot reconcile changes.” This notification links directly to the page with the conflict. - Open the affected page
Click the notification to open the page. Notion highlights the conflicting blocks with a red border and a warning banner at the top of the page. - Review the conflict resolution dialog
Click the red banner or the block itself. A dialog box appears showing the two conflicting versions side by side: “Your version” and “Server version.” Read both versions carefully. - Choose which version to keep
Click “Keep my version” to apply your offline edits. Click “Keep server version” to discard your changes and keep what is on the server. After you choose, Notion merges the selected version and removes the conflict flag. - Check for additional conflicts on the same page
Scroll through the entire page. Each conflicting block appears with its own red border. Repeat steps 3 and 4 for every conflict on the page. - Confirm the page syncs successfully
After resolving all conflicts, the red banner disappears. The page icon shows a green check mark in the sidebar, confirming the sync is complete.
If Notion Still Has Issues After the Main Fix
Conflict notification does not appear after reconnecting
If you do not see a conflict notification but the page still shows sync errors, force a manual sync. Click the page icon in the sidebar, then press Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac to refresh the page. Alternatively, close and reopen the Notion app. The conflict dialog should appear after the refresh.
Conflict dialog shows the same version in both panels
This occurs when Notion already applied one version but still flags a conflict due to a metadata mismatch. Click “Keep my version” to clear the flag. If the dialog does not close, duplicate the page by clicking the three-dot menu next to the page title and selecting “Duplicate.” Delete the original page and work from the duplicate.
Database rows show blank values after resolving conflict
When you keep the server version for a database cell, Notion may discard the entire row if the offline edit affected the row’s primary key or unique identifier. To recover the data, open the page version history by clicking the clock icon in the top-right corner and restoring the version from before the offline session.
Notion Sync Conflict Resolution: Offline vs Online Behavior
| Item | Offline Edit Session | Online Collaborative Edit |
|---|---|---|
| Change recording | Stored locally as a pending change set | Sent to server immediately per keystroke |
| Conflict trigger | Any edit to a block also changed by another user during offline period | Only simultaneous edits to the exact same block within seconds |
| Merge method | Manual selection via conflict resolution dialog | Automatic last-write-wins for text; manual for database properties |
| Notification | Bell icon + optional email alert | Real-time banner on the page |
| Recovery option | Version history available after conflict is resolved | Version history available at any time |
You can now identify and resolve Notion sync conflicts caused by offline editing. When you plan to work offline, enable the “Sync conflicts” notification toggle in Settings & Members > Notifications to get immediate alerts after reconnecting. As a preventive measure, avoid editing database cells or page titles when you know you will be offline for an extended period — those edits trigger the most conflicts.