QUICK ANSWER
Keep every version until you know what each one contains.
Stop writing on the affected note on both devices. Let any active sync finish, then turn off Auto Sync while you inspect the copies. Do not delete, rename or move the original and conflict file yet.
Copy both files to a computer, record which device each came from and compare the newest pages. After preserving the content, follow Supernote’s official sequence: sync the device you just used, wait for completion, then sync the second device before opening or editing the note there.
WHAT THE WARNING MEANS
Two devices presented changes that Supernote could not safely combine
Supernote’s cross-device guide tells owners not to edit, rename, move or copy the same file on a second device before the first device has completed syncing. When two versions compete, a conflict copy can preserve one branch instead of silently choosing a winner.
Recent Manta and Nomad owner reports describe repeat conflict files and, in some cases, uncertainty about missing recent work. These reports show a real support problem, but they do not tell us how often it happens or prove that every conflict has the same cause.
Supernote’s August 2026 beta changelog says Chauvet 3.29.43_beta can detect and resolve files with sync conflicts. That confirms active work on the problem. It does not make beta software the safe first move when your notes are already at risk.
Preserve the files and contact Supernote first. A beta update changes the device while you are still trying to establish which copy is complete.
FIRST: PROTECT THE DATA
Freeze the situation before cleaning it up
- Stop editing the note on both devices.Close it and return to Files. Do not add a test stroke because that creates another changed version.
- Wait for any visible sync to finish.Do not interrupt an active upload. Once it completes, turn off Auto Sync while you inspect the files.
- Record what exists on each device and in the cloud.Photograph the filenames and folders. Include modified times, file sizes and any “CONFLICT” suffix.
- Copy every candidate to a computer.Supernote documents USB transfer for files and folders. Put the Manta and Nomad copies in separately named, dated folders.
- Keep the cloud copy unchanged.Do not delete a cloud file to force a re-download. Sync can carry that deletion back to both devices.
This is containment, not a promise of recovery. If a recent page is missing from every copy, stop and send logs to Supernote before resetting, signing out or doing more sync tests.
COMPARE, THEN DECIDE
The newest timestamp is not enough
Opening a file or completing a sync can affect metadata, so treat the modified time as a clue rather than proof. Compare the content that matters and make notes outside Supernote while you inspect.
Open each copy without editing and find the newest complete page you recognize.
A larger count can reveal added pages, but it does not prove every page is newer.
Check recent headings, links, keywords and calendar items, not only handwriting.
Record each filename, location, size and modified time before renaming anything.
If one file clearly contains all recent work, keep the untouched computer copies and choose that complete file as the candidate to return. If each version has unique pages, do not overwrite either one. Export readable PDFs for reference and ask Supernote whether the native files can be recovered or combined.
Changing the conflict file back to the original name can hide which version came from which device. Rename only after you have an independent copy and a written record of the contents.
CONFIRMED PREVENTION
Use a strict handoff between Manta and Nomad
Supernote’s official method is sequential. Finish with one device before the other touches the same note:
- MANTAFinish editing and return to Files.
Returning to Files is also the trigger Supernote documents for Auto Sync when it is enabled.
- MANTASync and wait for 100% completion.
Do not open, rename or move the same file on the Nomad while this is happening.
- NOMADSync before opening the note.
Confirm the incoming version is present. Only then begin the next editing session.
- NOMADFinish, return to Files and sync again.
Reverse the handoff when you go back to the Manta.
Some owners reduce exposure by selecting different folders for each device or treating one device as read-only for certain notebooks. Supernote’s transfer guide confirms that folders can be selected for Supernote Cloud sync. This can be a practical workaround, but it is not the same as repairing conflict handling.
WHEN THE CONFLICT RETURNS
Send logs from both devices before destructive steps
If a conflict returns after a clean sequential handoff, or if either copy is missing recent pages, use Settings > Feedback on both the Manta and Nomad and include system logs. Give Supernote the exact filenames, folder paths, time and time zone, cloud provider, installed Chauvet version, sync order and the point at which the copies diverged.
Do not factory-reset either device, remove the cloud account, clear storage, delete cloud files or repeatedly sync to “see what happens.” Those actions can remove evidence or spread the wrong version.
Check the stable Manta and Nomad changelog before updating. The conflict-resolution feature was still documented on the beta page when Yeinks checked on October 8, 2026, so ask Supernote whether a newer stable release applies to your case rather than assuming.
SOURCES
Official guidance and reporting limits
Supernote documentation and recent owner reports were checked on October 8, 2026. Owner reports were used to identify symptoms and edge cases, not to estimate a failure rate. Yeinks has not reproduced the conflict and has not tested the beta release.