Troubleshooting
Google Docs Connected, But Agent Can’t Edit?
A deterministic fix flow for “connected but still read-only” Google Docs loops.
Common pattern: the agent can find your Google Doc, maybe even quote it, but fails when asked to insert text, rewrite sections, or apply edits.
Reality check: “Connected” is not edit proof. You need one successful canary write to the exact document in the exact session/surface.
Fast path (4 steps)
1) Confirm account + exact document
Most failures are wrong Google account, wrong copy of the doc, or wrong folder context. Confirm the exact doc title and owner account first.
2) Verify document permission level
The connected account must have Editor access, not Viewer/Commenter. Shared docs often look editable in UI but are restricted for the connected identity.
3) Run a tiny canary write
Use one non-destructive edit and require proof output:
Append this exact line to the end of the document:
"CANARY_EDIT_OK - [today's date]"
Then return:
- Document title
- Exact inserted text
- Approximate location (end of doc / section heading)
- Any raw error text if write failed
4) Only then do large edits
Don’t request full rewrites until canary write succeeds in the same surface/thread where you plan to work.
Copy/paste recovery prompt
My Google Docs connector appears connected, but edits are failing.
Do this exactly:
1) Confirm the authorized Google account.
2) Confirm the exact target document title.
3) Perform ONE canary write: append "CANARY_EDIT_OK - [today's date]".
4) Return proof: document title + inserted text + location.
5) If it fails, return exact raw error text and stop.
6) Do not reconnect unless you show a specific auth/scope/permission error.
High-friction failure patterns
- Viewer/Commenter mismatch: you can open the doc but cannot edit.
- Wrong account: connector is authorized to a personal account while doc lives in workspace account.
- Duplicate doc names: edits are applied to a different file with the same title.
- Cross-surface mismatch: connector linked in one context, edit requested in another session/thread.
Advanced edge cases
- Org policy restrictions: Google Workspace admin rules can block app-based document editing.
- Scope mismatch: OAuth may allow read/list access but not write/modify scope.
- Protected sections or document locks: parts of the doc may be blocked by template controls or concurrent edit state.
- Stale auth state: reconnect appears successful, but current session still uses old token context.
Loop-break rule
Stop reconnect spirals: run one reconnect max per diagnostic cycle. If canary write still fails, escalate once with exact evidence.
What to include if you escalate
- Authorized Google account shown by the agent
- Exact target document title
- Requested canary text
- Surface/context (dashboard, DM, channel, thread)
- Exact raw error message (no paraphrase)
Bottom line: prove one canary write to the exact doc. If that works, scale up. If it fails, escalate with precise evidence once.