Conflict resolution
How 2sync handles simultaneous changes across platforms
When you edit the same item in both Notion and an external app between sync cycles, a conflict occurs. 2sync resolves conflicts automatically at the field level using your sync direction settings, so no data is silently lost. Understanding how conflicts resolve helps you design reliable automations.
How does 2sync resolve conflicts?
2sync evaluates conflicts per field, not per item. If you change the title in Notion and the date in Google Calendar, both changes apply because they affect different fields. Conflicts only arise when the same field is modified on both sides.
What happens with two-way fields?
For fields set to two-way sync, both platforms are monitored for changes. When 2sync detects changes on both sides, it applies updates in both directions based on field-level sync direction settings. Both Notion and the external app receive the other side's changes.
For example, if you update the event title in Notion and the description in Google Calendar between syncs, both changes apply because they affect different fields. If the same field changes on both sides, 2sync applies updates in both directions based on your field-level direction settings.
What happens with one-way fields?
For fields configured as one-way, only changes from the designated source apply. Edits on the non-source side are ignored during sync.
For example, if "Organizer" is set to one-way from Google Calendar to Notion, any manual edits to the Organizer field in Notion are overwritten on the next sync.
How does field-level direction help?
2sync lets you set sync direction per individual field, not just per automation. This gives you granular control over conflict behavior.
| Field | Direction | Conflict behavior |
|---|---|---|
| Event Title | Two-way | Both sides' changes applied |
| Date | Two-way | Both sides' changes applied |
| Organizer | One-way to Notion | Google Calendar always wins |
| Custom Status | One-way to Calendar | Notion always wins |
Configure field directions in your field mapping settings.
Set informational and metadata fields (organizer, created date, sync status) to one-way sync. This is the most effective strategy for preventing conflicts because it removes those fields from two-way contention entirely.
How do I minimize conflicts?
Edit in one place at a time: The simplest way to avoid conflicts is to make changes in one app and wait for the sync to complete before editing in the other.
Use faster sync frequencies: Shorter intervals (2-3 minutes on Premium and Pro plans) reduce the window where conflicts can occur.
Set non-editable fields to one-way: Fields you never edit in one platform should sync one-way from the other. This eliminates conflict potential entirely for those fields.
Check sync status before bulk edits: If you plan to make many changes, click Sync Now first to ensure everything is current, then make your edits in one platform.
Avoid editing the same field in both Notion and the external app within the same sync interval. While 2sync handles this gracefully using field-level direction settings, editing in one place at a time produces the most predictable results.
What does conflict resolution look like in practice?
Here is a concrete example of how 2sync resolves a conflict for a Google Calendar event.
Setup: A two-way sync between Google Calendar and Notion. The event "Q1 Planning" exists in both platforms. Sync runs every 3 minutes.
Between sync cycles, both sides are edited:
- In Google Calendar: the location is changed to "Room 4B" and the description is updated
- In Notion: the title is changed to "Q1 Planning - Final" and the description is updated with different text
How 2sync resolves each field:
| Field | Changed in | Resolution | Reason |
|---|---|---|---|
| Title | Notion only | Notion value applied to Google Calendar | Only one side changed |
| Location | Google Calendar only | Google Calendar value applied to Notion | Only one side changed |
| Description | Both sides | Resolved by field direction setting | Same field changed on both sides |
The title and location merge cleanly because they were edited on different sides. The description is a true conflict because both sides changed it. 2sync applies the update based on whether the description field is set to two-way, one-way to Notion, or one-way to Google Calendar.
Related
- Sync direction for configuring per-field direction to prevent conflicts
- Two-way vs one-way sync for choosing a direction that minimizes conflicts
- Filters for controlling which items sync
- Activity logs for reviewing conflict resolution history
FAQ
Does 2sync merge conflicting changes?
2sync does not merge at the text level within a single field. When the same field changes on both sides, updates are applied in both directions based on your field-level sync direction settings.
Can I see when a conflict was resolved?
Check your automation's activity log. It records every change applied during sync, including which value was used when a conflict occurred.
What if I want Notion to always win conflicts?
Set all fields to one-way from Notion to the external app. This makes Notion the sole source of truth and eliminates conflicts entirely.
Do conflicts cause errors?
No. Conflicts are resolved silently based on field-level sync direction settings. They do not trigger error statuses or pause your automation.