What calendar sync actually does, and why it sometimes looks broken
A calendar app does not own your events. It shows you somebody else's copy, and the gap between those two facts is where confusion lives.
What most people assume
That events live in the app you created them in.
The app is a window
Your events live on Apple's servers, or Google's, or your employer's. The app on your phone holds a cache and reconciles it. Delete the app and the events survive; delete them in the app and they are gone everywhere.
This is why the same calendar looks identical on your phone and your laptop: neither is the original.
Why changes take a moment
A change is written locally first so the interface stays quick, then pushed. If the network is poor, the local copy is ahead of the server for a while — which is correct behaviour that looks like a bug.
Two devices editing during that window is the one genuinely awkward case, and it is rarer than people fear.
What you can and cannot fix
Missing events are almost always a permission or a selected-calendars problem rather than a sync failure. Check what the account is actually sharing before assuming the connection is broken.
Duplicates usually mean the same calendar arrived twice by different routes — a Google account added directly and again through iCloud, for instance.
The numbers
| What it describes | Value |
|---|---|
| Account types kept in sync | 3 |
What it looks like
What to do
- If events are missing, check which calendars the account is publishing before reconnecting anything.
- If events are duplicated, look for the same calendar arriving by two routes.
- Give a change a moment before deciding it failed, especially on a weak connection.