When two calendars disagree about the same event
Two devices, one event, two different times. It is unsettling precisely because a calendar is supposed to be the thing you can trust.
What most people assume
That a conflict means something is broken.
Usually it is a race, not a fault
Both edits were valid; they simply happened before either device heard about the other. The server keeps the one that arrived last, which may not be the one you meant.
This needs no repair. It needs you to decide which version is right and say so once.
The duplicate that is not a conflict
Far more common than a genuine conflict is the same event arriving twice by two routes — subscribed once directly and once through another account. Nothing is in conflict; you are simply seeing one event twice.
The fix is to stop one of the routes rather than to delete an event, which would remove both copies.
What it looks like
What to do
- Decide which version is correct and set it once, from one device.
- For duplicates, find the second route before deleting anything.
- If a change refuses to stick, check whether the calendar is read-only for you.