Google Calendar and Outlook not syncing: narrowing down the cause

When Google Calendar and Outlook stop agreeing with each other, the first instinct is to remove the connection and set it up again. That sometimes works, and it hides the reason, which means the same problem returns a few weeks later. Most cases fall into one of four causes, and they can be separated in a few minutes without deleting anything. Two of them are not faults at all: they are the documented behaviour of the method that was used, working exactly as designed.

Decide which direction is broken

Before changing any setting, establish which way the events are failing to travel. The answer narrows the possible causes immediately, and it is the step most often skipped.

Create a test event in Google Calendar with a distinctive title and a time tomorrow. Create a second test event in Outlook. Wait, then look at both applications. There are four possible outcomes and each points somewhere different.

If the Google event never appears in Outlook, the connection either does not exist or is stale. If the Google event appears in Outlook but the Outlook event never appears in Google, the link is one way, which is normal for one of the two available methods. If edits made in Outlook to a Google event silently revert or refuse to save, the calendar is attached read only. If both events appear but hours later than expected, nothing is broken and the refresh interval is being observed.

Most people arrive at this point having assumed the first case and actually having the second or fourth. Running the test takes a few minutes and prevents a rebuild that would not have helped.

Cause one: the calendar was imported, not subscribed

This is the single most common explanation, and it comes from two menu items that sit next to each other and do very different things. Microsoft's documentation on the difference is unambiguous.

When you import an .ics file, you get a snapshot of the events in the calendar at the time of import. Your calendar doesn't refresh the imported events automatically, even if the calendar's owner makes an update. Source: support.microsoft.com

Downloading a Google calendar as a file and uploading it to Outlook produces a set of events frozen at the moment of upload. Nothing about that arrangement is ever going to update, and there is no setting that will make it update. The events look correct for the first few days, which is precisely why the problem is usually noticed weeks later, when a meeting that moved is still showing at its original time.

Subscribing is the other option. In Outlook.com the two live under Add calendar, as Subscribe from web and Upload from file. Subscribing takes a URL and keeps following it. Uploading takes a file and stops.

The way to tell which was done, without guessing, is to change an event in Google Calendar and wait a day. If the change never crosses, and the calendar in Outlook was added from a file, the diagnosis is settled. The repair is to remove the imported calendar and subscribe to the URL instead, accepting that the events already imported have to be cleared out separately.

Cause two: it is syncing, on a schedule longer than expected

Subscribed calendars do not update the moment something changes. Microsoft documents both the normal interval and the worst case.

This update can take more than 24 hours, although updates should happen approximately every 3 hours. Source: support.microsoft.com

Roughly three hours as the usual case, and more than twenty four hours as a possibility, is a very different thing from the near instant behaviour people expect after using a phone calendar. A meeting moved at nine in the morning and checked at nine fifteen has not failed to sync. It has not been collected yet.

This matters beyond patience. A subscribed calendar is not a safe basis for a same day scheduling decision, because the copy being looked at may be hours old. Anyone coordinating meetings that get rearranged during the day is relying on a feed that was never designed for it. That is an argument about which method to use rather than a fault to fix, and it is the reason the account based connection covered below is worth the extra setup.

Cause three: the link is read only by design

Google documents two distinct ways to bring a calendar into another application, and the choice made at setup time decides whether editing is possible at all.

With some calendar applications, you can sync your calendar using your Google Account. This means you can add and edit events from either Google Calendar or your other application. Source: support.google.com

Signing in with the Google account gives a two way connection. Using the iCal link, which Google labels the secret address in iCal format, gives a view. Google describes it as the route for applications without a full sync option, or for when a read only view of one calendar is wanted.

The symptom is specific and easy to recognise once known. Events appear correctly, the calendar looks completely normal, and then an attempt to drag an event to a new time either fails outright or appears to succeed and reverts. Nothing is corrupted. The calendar was attached as a copy, and a copy has nowhere to send an edit.

The same mechanism explains the complaint that events created in Outlook never reach Google. A subscription carries data one way only. If events need to exist in both places, the setup has to be the account connection, not the URL.

Cause four: something outside the calendar changed

When a connection worked for months and then stopped, the cause is usually not in either calendar application.

Access was revoked. A changed password, a security review, or an administrator removing third party access will break an account connection without producing a clear message. The connection simply goes quiet, which reads as a sync bug.

The secret address is no longer available or no longer valid. Google notes that if the account belongs to a work or school organisation, an administrator may have changed the sharing settings, in which case the secret address may not be visible at all. Resetting the address, which Google offers as the fix for an address shared by accident, also invalidates the old one. Any subscription still pointing at the previous address stops receiving updates and gives no warning.

A public address was used on a calendar that is not public. Google states that the public iCal address only works if the calendar is public. A subscription built on that address will fail as soon as the calendar stops being public.

The change is in flight. Sharing changes are not instant either. Google notes that removing public sharing usually takes a few minutes but can take up to four hours to take effect, so a test run immediately after a permissions change can show the old behaviour.

When the complaint is duplicates rather than gaps

Not every sync problem presents as a missing event. The opposite symptom, where every meeting appears twice or three times, has a different cause and is worth separating out, because the usual repair for missing events makes duplicates worse.

Duplicates come from more than one route into the same calendar. A Google calendar subscribed by URL, and the same Google account also connected by signing in, produce two independent copies of every event. Neither route knows about the other, so neither considers the result a conflict. The same thing happens when an .ics file was uploaded at some point and a subscription was added later: the frozen copy stays where it is and the live copy sits on top of it.

Invitations add a third route. A meeting organised in one account and sent to the other arrives as an invitation, creating a legitimate event, while the calendar carrying the organiser's copy also shows it. Both are real, and deleting one can send a cancellation to the other attendees, which is why duplicates deserve care rather than a quick clean up.

The way through is to list every connection before deleting any event. In Outlook, look at the calendar list and identify where each entry came from. In Google Calendar, check the calendars on the left for anything subscribed from an external address. Remove the redundant route, not the events, and let the surviving route reflect the truth.

The deeper problem is that every additional route is another copy with its own refresh schedule, and copies drift. A week read from three copies of the same calendar is slower to interpret than a week read from the accounts themselves, which is the practical case for keeping a single window over each connected account. Details of how events are entered once and land in the right place are in the Entering events notes.

Matching the symptom to the cause

What is seen	Most likely cause	What to check
Nothing has updated in weeks	Calendar was uploaded from a file	Whether it was added under Upload from file rather than Subscribe from web
Changes arrive, several hours late	Normal subscription refresh	Nothing. Roughly every three hours, possibly longer than a day
Events cannot be edited in Outlook	Attached by iCal link	Whether the account was connected by signing in, or by URL
Google events reach Outlook, not the reverse	One way subscription	Same as above. A subscription cannot carry edits back
Worked for months, then stopped	Access revoked or address reset	Password changes, administrator policy, whether the iCal address was reset
Only some calendars are missing	Sharing or visibility, not sync	Whether the calendar is public, and whether the secret address exists

The table divides into two halves worth naming. The top rows are documented behaviour that no amount of reconfiguring will change, and the bottom rows are genuine breakages with a specific thing to inspect. Deleting and recreating the connection only addresses the bottom half, which is why it works about half the time and teaches nothing either way.

There is also a structural point underneath all four causes. Keeping two calendar services in agreement through a URL means accepting a delay measured in hours, and keeping them in agreement through an account connection means one of the two is the place where events are actually created. A desktop calendar that connects to each account directly and shows them in one window sidesteps the question, because there is no copy to fall behind. What that kind of application handles is listed on the Features page, and the Compared with other calendars page sets out the Mac options on price and capability.

What to change first

Find out whether the calendar in Outlook was uploaded from a file or subscribed from the web, because that one fact decides three of the four cases above. If it was a file, replace it with a subscription. If two way editing is needed rather than a view, connect the account instead of the URL, and if the delay of a feed is the real problem, a native Mac calendar that talks to each account directly is Caltimate.