> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Google Meet Troubleshooting
> Common failure modes for the Rootly AI Meeting Scribe bot on Google Meet — service accounts, workspace admin settings, and admission failures.
## Overview
The Meeting Scribe joins Google Meet as an external participant. Getting it to join reliably comes down to two things: **how you connected the integration** (personal OAuth vs. service account), and **what your Google Workspace admin has locked down**.
For the full Meeting Scribe reference, see **[Rootly AI Meeting Scribe](/ai/meeting-scribe)**.
***
## Use a Service Account for Production
The single biggest lever for reliable Google Meet scribe behavior is connecting via a **Google Cloud Service Account** rather than personal OAuth.
| Connection type | Reliability | When to use |
| ------------------- | -------------------------------------------------- | ---------------------------- |
| **Service account** | High — domain-wide, stable across staff changes | Production incident response |
| **Personal OAuth** | Fragile — tied to one user's token and permissions | Quick testing only |
**Fix if you're on personal OAuth:** Reconnect the integration via a service account. See [Google Meet → Installation](/integrations/google-meet/installation) for the setup flow.
***
## The Bot Won't Join Google Meet Meetings
Walk through this list in order.
### The integration is on personal OAuth (not a service account)
Personal-OAuth connections work but are tied to one user. If that user's token expired or they lost calendar permissions, the scribe stops being able to admit itself to calls.
**Fix:** Reconnect via a service account (see above).
### The meeting URL wasn't created by Rootly
The scribe is scoped to the Google Meet room Rootly created for the incident. Ad-hoc `meet.google.com` links or personal meeting rooms won't be picked up.
**Fix:** Use the meeting link Rootly pinned at the top of the incident's Slack channel.
### Google Workspace Meet safety settings block admission
Even with a service account, the scribe can fail to join if your Google Workspace admin has restrictive Meet safety settings enabled — specifically the **Host management** setting.
When Host management is on, only the meeting host can admit external participants. The scribe joins as external, so it sits in the lobby waiting for a host to admit it (and hits the waiting-room timeout).
**Fix:** In the Google Admin console, go to **Apps → Google Workspace → Google Meet → Meet safety settings** and turn **Host management** off for the organizational unit that runs incident bridges. Guests will still be moderated by the meeting itself — this setting only controls whether non-hosts can admit external participants.
***
### Waiting-room timeout (10 minutes)
If the scribe is stuck waiting for admission and no one lets it in, it leaves after **10 minutes**.
**Fix:** Reinvite from the **Meeting** tab and admit it promptly. Prevention: service account + turn off **Host management** in your Meet safety settings (see the section above).
### Nobody-joined timeout (5 minutes)
If the scribe enters the meeting but no responders join within **5 minutes**, it leaves.
**Fix:** Start the meeting on your side first, then reinvite the bot — or wait until responders are on the call before inviting it.
***
## The Bot Joined but Transcript Is Missing
### Post-meeting processing is still running
Transcripts and Rootly AI meeting summaries generate after the call ends. Give it 5–10 minutes.
### Recording started but the call ended abruptly
If the meeting host ended the call while the scribe was still in an unstable state, some of the recording may not have made it to processing. Reinvite for future sessions of the same incident if the meeting resumes.
### The bot recorded a "waiting room" clip and nothing else
The bot was never admitted to the meeting — the recording is only its own waiting-room view. See the "won't join" section above for the underlying cause.
***
## Frequently Asked Questions
Service accounts represent your Google Workspace organization rather than a specific user. They don't need a personal OAuth grant to keep working, they don't lose access when someone leaves the team, and they behave consistently regardless of who declared the incident. Personal OAuth ties the scribe to whoever connected it — one departure and reliability drops.
Only one Google Meet connection is active at a time. Switch by reconnecting.
The scribe joins meetings hosted on your Google Workspace domain. Meetings hosted by an external organization (a vendor, a partner) can't grant your scribe entry unless their admin admits it, which is unusual.
No. Meeting Scribe is scoped to your Google Workspace domain. Meetings created by a personal `@gmail.com` account aren't covered.
***
## Related Pages
Full Meeting Scribe reference — limitations, retention, subprocessors, security.
Everything the Google Meet integration does beyond the scribe.
Connect your Google Meet account, including the service account flow.
The equivalent page for Zoom.