Why Google calendar integration breaks and how to fix it

Modified on Sat, 26 Oct at 9:35 AM

The most common reasons when Google integration breaks

The Google connection expires due to password change and some other reasons you can find here Google OAuth2 Expiration.

Due to the connection issue, the main (refresh) token expires. In general, in an ideal situation, the refresh token from Google was never intended to expire unless these are the reasons Google OAuth2 Expiration.

You just need to reintegrate the Google connection and all should be fine. It happens when Google revokes our access token due to you or a user whose Google account is connected changing their Google password or some change in the Google account.

Not just appointments, all other events/data also stay and won’t be deleted unless the calendar is deleted. The re-integration never affects any existing platform data except token refresh (oAuth).

We do not add the error banner for all the calendars; that will only be true of all the calendars with that Google account synced to it, and all should be fine when you reintegrate your Google connection. Any of the synced appointments will not be affected due to this.

How to fix it for an unassigned calendar:

If you remove the linked calendar from the platform calendar with the trash icon next to where you add a synced Google calendar, it will remove all non-platform events, but in this case, you don’t need that. This is just for info.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article