Google Drive connector PDF upload issue

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

The Google Drive connector’s create_file can’t reliably upload ~40–54KB PDFs. As base64Content, the payload gets truncated or corrupted: one file landed 60 bytes short, others came through as 8-byte junk or a few KB instead of ~46KB. Tiny test PDFs upload fine. A couple of attempts also hit Auto-review with “An error occured while classifying this action. Please review manually.” Please fix create_file so a real PDF (tens of KB) can go through intact.

Steps to Reproduce

The Google Drive connector’s create_file can’t reliably upload ~40–54KB PDFs. As base64Content, the payload gets truncated or corrupted: one file landed 60 bytes short, others came through as 8-byte junk or a few KB instead of ~46KB. Tiny test PDFs upload fine. A couple of attempts also hit Auto-review with “An error occured while classifying this action. Please review manually.” Please fix create_file so a real PDF (tens of KB) can go through intact.

Operating System

MacOS

Version Information

Version: 0.30.0
Release Track: stable
OS: darwin

For AI issues: add Request ID with privacy disabled

237e57f2-5381-476f-9cbc-d3e67aed3f61

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report with the size breakdown. That really helps.

This is a known issue we’re already tracking. The Drive connector currently sends the file contents as base64 inside the tool call itself, and payloads in the tens of KB are unreliable on this path. That’s why tiny test PDFs upload fine, but 40 to 54 KB files get truncated or arrive corrupted. The auto-review message “An error occured while classifying this action” on some attempts is a related symptom of the same large tool calls, and we’re tracking that too.

For now, one of these two workarounds usually works:

  • Ask the agent to send the PDF as a chat attachment, then upload it to Drive yourself.
  • Ask the agent to upload the file using its own browser at drive.google.com. You’ll need to log in to Google once.

I can’t share an ETA for a fix yet, but I’ll post an update here if I have one.