Learning level
99/100
Conflict Resolution
VauSheet · 81–100 · Advanced Architecture & SupportProduct version
1.0.1
Guide status
Stable
Sections
5
Conflict Resolution
Implementation-backedResolve genuine same-path workbook conflicts using Keep Mine or Use Latest without discarding unrelated mergeable edits.
What this guide covers
Why a conflict can occur
Automatic merge first
Keep Mine
Use Latest
Quick facts
Version1.0.1
SurfaceWeb browser
StorageCloud + local checkpoint
ThemeLight · white/orange
Documentation rule: this VauSheet section describes the current implemented product behavior. It avoids claiming full Microsoft Excel parity or live-cursor collaboration where the current build does not provide it.
01
Why a conflict can occur
A conflict can occur when two devices edit the same workbook from compatible base state and their changes overlap at a path/cell that cannot be safely auto-merged.
02
Automatic merge first
The synchronization service uses semantic workbook patch/three-way merge behavior so non-overlapping remote and local changes can be combined without presenting a conflict for every concurrent edit.
03
Keep Mine
Keep Mine retries synchronization with conflict overwrite enabled for the conflicting local paths while still using the server synchronization flow.
04
Use Latest
Use Latest reloads the newest metadata + stored workbook, replaces the local conflicting workbook and establishes that remote version as the new synchronized base.
05
Choose carefully
Use Keep Mine when your local conflicting edits are the intended source of truth. Use Latest when the newer cloud version should win.
Updated 2 Sep 2026VauSheet 1.0.1