Save your newest changes before changing anything
The most important decision in a sync incident is which copy contains the latest edits. OneNote can show an older notebook in the browser while a desktop copy still has unsynced work. Microsoft recommends opening the notebook in a browser to check whether its contents contain your most recent changes. If they do not, inspect the device where you made those changes. Copy important unsynced notes to a separate safe location before signing out, closing notebooks, recreating sections or moving content. Closing and reopening notebooks can help in some circumstances, but it should not be the first experiment on the only recent copy.
Record the notebook name, which account is signed in, and the exact error code. Those details distinguish a network problem from a quota or section-specific failure. A general message such as ‘Sync error’ is insufficient for selecting a targeted repair. Shared notebooks can produce a different outcome on each device while the connection is unreliable.
Find the failing notebook or section
In supported OneNote desktop versions, Microsoft describes File > Info > View Sync Status. This shows sync status and error codes. Check whether the warning concerns the whole notebook or one section. If the web view is current and one local page is not, the problem may be on the originating device; if the web view is stale everywhere, investigate the account and service connection before assuming the work was deleted.
For a notebook with a warning icon, use the sync status interface to inspect the failing location and consider the offered Sync Now action. Some variants also expose a help button with a corresponding error-code article. Avoid repeatedly forcing synchronization without reviewing the error: the correct response to a storage quota warning differs from a temporary service error.
Safely investigate a single bad section
Microsoft documents a section-level workaround: create a new section inside the same notebook, copy — do not initially move — affected pages into it, then manually sync. Check the browser copy before deleting or renaming the old section. This copy-first sequence retains a fallback if the new section does not sync or contains an older page version. The menu labels for moving and copying sections differ among Windows, Mac and web editions, so follow the controls on your installed client.
If OneNote generates a conflict or merge-conflict page, it may hold edits by a second person to the same area. Review both versions and manually combine the intended changes into the main page. Do not press a deletion action on the conflicting version until you have compared the content. Microsoft’s support article notes that multiple page copies may exist specifically to avoid data loss during simultaneous edits.
Common mistakes to avoid
A section visible in the Notebook Recycle Bin is not equivalent to a section that simply fails to sync. A misplaced section can happen when OneNote cannot find its expected location and may still contain valuable changes. If you see a misplaced section, prefer a move to the correct notebook over permanent deletion while you are investigating. Likewise, the presence of a copy on a phone does not prove the browser has the same revision.
A practical example
You added a dozen bullet points on a laptop during a train ride. Later the web version lacks the last five. First export or copy those five from the laptop; do not close that notebook yet. Check the laptop’s sync status and record its error code. Once you have a safe copy, try a targeted retry using the application’s sync controls. If only one section fails, create a new section and copy pages across, then check the browser. Only after the cloud copy matches should you clean up duplicates.
Final verification
Open the same notebook in OneNote on the web and on the editing device. Compare a recognizable line from your newest work rather than trusting the absence of a warning icon alone. For collaborative notebooks, ask a teammate to verify the page if appropriate. Keep your recovery copy until you know all editors can see the same changes. This site offers a checklist, not access to your Microsoft account or its synchronization logs.
Official references
Links below point to first-party documentation. Our scenarios and wording are independently written.