Hey everyone, hoping to get some advice or see if others are hitting this same wall.
We’ve been rolling out Fellow across our engineering teams, and the Google Calendar sync seems to be broken for about half our users. For some, meetings sync once and then never update; for others, new meetings just don’t appear at all. We’ve done the usual dance—cleared caches, re-authenticated, toggled the sync off and on. No luck.
Our ticket with support has been open for over a week with only generic “we’re looking into it” replies. In the meantime, our meeting hygiene is falling apart because the agendas aren’t attached to the right calendar events 😅.
Has anyone else experienced this recently? I’m curious:
- Are there known issues with certain Google Workspace configurations?
- Has anyone found a workaround that actually sticks?
- If you moved past this, was it something on Fellow’s side or did you need an admin to tweak something in Google?
I can share that our setup is pretty standard: OAuth via Google Workspace, using the default calendar permissions. Nothing fancy in our Terraform for GCP that should interfere, but you never know.
Really hoping to crowdsource a fix here—our retro meetings are feeling the pain!
~CloudOps
Infrastructure as code is the only way
Oh wow, that sounds super frustrating, especially with support being slow. 😬
> "Our ticket with support has been open for over a week"
This might be a long shot, but have you checked if the affected users are all on the same Google Calendar release track? I've seen weirdness with the "Rapid Release" vs "Scheduled Release" tracks in Workspace before, though usually with Asana syncs.
Also, maybe a dumb question from a newcomer, but does Fellow have a sync log or diagnostic area for users to check? Wondering if the errors are consistent.
I doubt the release track is the issue. Google's API is the API, the track just changes the UI.
> does Fellow have a sync log
They usually don't, and that's the problem. You're blind. You have to guess between OAuth token weirdness, service account quota exhaustion on their side, or their sync engine just falling over for a subset of users. Without logs, you're stuck pestering their support.
Don't panic, have a rollback plan.
You're right about the visibility problem. When sync fails silently, teams waste days guessing. I've found that creating a simple health check script on our side can sometimes force the issue into the light.
For example, we had a similar sync issue where the root cause ended up being intermittent API quota errors from the service provider. We only spotted the pattern by logging a few key API responses from our own OAuth flow before the data hit their system. It might be worth asking the affected users to check their Google Cloud console for any unusual auth activity or errors, just to rule that layer out.
ship early, test often