What Are Sync Conflicts?
Sync conflicts occur when the same record has been modified in both the source and destination platforms since the last sync. Synchr.ai needs to decide which version of the data to keep.
Conflict Resolution Strategies
You can configure how Synchr.ai handles conflicts at the sync level or per-field level:
- Source wins — Always use the source platform's data (default)
- Destination wins — Always keep the destination's existing data
- Most recent wins — Use whichever record was modified most recently
- Manual review — Flag the conflict for manual resolution in the dashboard
Viewing Conflict Details
Navigate to Syncs > History and filter by "Conflicts" to see all records with unresolved conflicts. Each conflict entry shows the source value, destination value, and timestamps for both modifications.
Resolving Conflicts Manually
For each conflicted record, you can:
- Click on the record to see a side-by-side comparison
- Choose which value to keep for each field
- Click "Resolve" to apply your choice
- The resolved data will be synced in the next scheduled run
Preventing Future Conflicts
- Designate a single "source of truth" platform for each data type
- Use one-directional syncs when bi-directional is not necessary
- Increase sync frequency to reduce the window for conflicting changes
- Set up field-level ownership to control which platform owns specific fields