Synchronization conflicts are uncommon, but they can occur when the same pipeline has been modified on multiple devices before those changes have been synchronized.
When this happens, Bethemesh never replaces one version with another automatically. Instead, it protects your work by letting you decide which version should be preserved.
What is a synchronization conflict?
A conflict occurs when two different versions of the same pipeline exist during synchronization.
For example:
- you edit a pipeline on your laptop;
- you later modify the same pipeline on your desktop computer;
- both devices synchronize afterwards.
Bethemesh detects that multiple versions of the same workflow now exist.
Why not merge them automatically?
Automatic merging may sound convenient, but it can introduce unexpected results.
A pipeline contains:
- modules;
- settings;
- execution order;
- connections between processing steps.
Automatically combining two independent versions could create an inconsistent or invalid workflow.
Instead of making assumptions, Bethemesh lets you choose.
Resolving a conflict
When a conflict is detected, Bethemesh displays every available version.
You can then:
- keep the local version;
- keep the synchronized version;
- compare both versions before deciding.
This ensures that you always remain in control of your workflows.
Preventing conflicts
A few simple habits greatly reduce the chances of encountering synchronization conflicts.
For example:
- synchronize regularly when working on multiple devices;
- finish editing on one computer before continuing on another;
- avoid modifying the same pipeline simultaneously on different machines.
In practice, these recommendations prevent the vast majority of conflicts.
Are conflicts common?
No.
Most users will never encounter one, especially if they primarily work on a single computer.
Even when using several devices, regular synchronization makes conflicts relatively rare.
Protecting your work
Bethemesh always prioritizes the safety of your work over aggressive automation.
Whenever uncertainty exists, the platform asks for your confirmation rather than risking the loss of important changes.
This approach reflects the same principles that guide the entire Local First philosophy.
In summary
Synchronization conflicts are a natural consequence of working on multiple devices.
Bethemesh detects them automatically, presents every available version, and lets you choose which one to keep.
This approach prioritizes reliability, transparency, and user control—core values of the Bethemesh platform.