Troubleshooting
Google Drive Connected, But Agent Can’t Find Files?
Fix the “connected but still unavailable” loop with a fast account/scope/session check and one tiny canary test.
Community pattern: users connect Google Drive, see “success,” then the agent still says it can’t access files. In most cases, this is not a broken connector — it is account mismatch, scope mismatch, or stale session state.
Important: “Connected” in one surface does not always mean every chat/session/thread is using the same authenticated context yet.
Quick reality check: yes, Google Drive access is possible — but it must be the Drive connector OAuth flow, not just creating a Gmail account for your agent. Community reports show many users get stuck by mixing those two ideas.
Fast path (5 minutes)
1) Confirm which Google account was authorized
Many users accidentally authorize personal Gmail while expecting workspace Drive (or vice versa). Re-open the connector and verify exact email.
2) Confirm Drive permission scopes were granted
If consent was interrupted or partially accepted, listing/reading files may fail silently. Re-run authorization and accept required Drive scopes fully.
2.5) Complete Google security prompts in one clean browser flow
Do not switch accounts mid-OAuth. Disable popup blockers for the auth step and finish every Google consent/security screen before returning.
3) Start a fresh chat/session before retesting
Old sessions can keep stale connector state. Open a new chat/thread and test there first.
4) Run a tiny canary query
Ask for one specific file or top 3 recent files, not a broad task.
List the 3 most recently modified files in my Google Drive and return filename + modified time only.
5) If still failing, capture exact error text
Do not paraphrase. Exact provider error text speeds support triage dramatically.
Known-good recovery prompt (copy/paste)
I need a strict Google Drive connector verification.
Rules:
- Do not guess.
- Return exact errors verbatim.
- Keep output short.
Steps:
1) Confirm whether Google Drive connector is currently available in THIS session.
2) If unavailable, say exactly what is missing.
3) If available, list 3 most recently modified Drive files (name + modified time only).
4) If listing fails, return exact provider error text and one next action only.
High-friction edge cases
- Wrong account authorized: connector succeeds but files “missing” because you connected a different Google account.
- Gmail vs Drive confusion: creating a Gmail account for your agent is not the same as completing Drive connector OAuth in the active workspace/session.
- OAuth security loop: Google security/consent screens were interrupted, blocked, or denied, so connector appears connected but cannot list files.
- Workspace admin policy restrictions: Drive API access can be blocked at org level even when personal accounts work.
- Surface mismatch: dashboard chat works, Discord thread fails (or vice versa) due to session/context differences.
- Shared Drive confusion: file is in Shared Drive but connector only sees My Drive scope/account context.
- Repeated reconnect loops: reconnecting repeatedly without fresh-session retest creates noise and hides root cause.
What not to do
Don’t: run long workflow prompts (“organize all my Drive files”) before a tiny canary passes. That burns tokens and makes diagnosis harder.
When to escalate
If canary fails after one clean reconnect + fresh-session test, send this support packet:
- Surface used (dashboard / Discord / thread)
- Exact Google account email authorized
- Exact error text (verbatim)
- What canary prompt you ran
- Timestamp + timezone
Bottom line: treat Google Drive setup as account + scope + session. Prove each one with a tiny canary, then scale up.