Hey Composio team, I’m seeing a Google Sheets values-read issue on the CLI. Environment: - Linux VPS - Composio CLI was 0.2.27, updated to 0.2.31 - Auth is valid, composio whoami works - Gmail, Calendar, Drive, and Sheets search tools all work - Issue is specifically with Google Sheets values reads What works: composio execute GMAIL_GET_PROFILE -d '{}' composio execute GOOGLESHEETS_SEARCH_SPREADSHEETS -d '{"query":"","max_results":1,"search_type":"name"}' After upgrading to 0.2.31, this single-cell read works: printf '%s' '{"spreadsheet_id":"","range":"Property Accounts!A1:A1"}' | timeout 75s composio execute GOOGLESHEETS_VALUES_GET -d - But multi-cell reads time out: printf '%s' '{"spreadsheet_id":"","range":"Property Accounts!A1:B1"}' | timeout 60s composio execute GOOGLESHEETS_VALUES_GET -d - Also times out: printf '%s' '{"spreadsheet_id":"","range":"Property Accounts!A1:Z1"}' | timeout 90s composio execute GOOGLESHEETS_VALUES_GET -d - And batch get also times out, even with camelCase args: printf '%s' '{"spreadsheet_id":"","ranges":["Property Accounts!A1:Z1"],"majorDimension":"ROWS","valueRenderOption":"FORMATTED_VALUE","dateTimeRenderOption":"FORMATTED_STRING"}' | timeout 90s composio execute GOOGLESHEETS_BATCH_GET -d - composio proxy to the Sheets values endpoint also times out. This started breaking cron jobs that read row 1 for schema/header resolution. It does not look like OAuth is revoked because auth works and Sheets search finds the spreadsheet. Could you confirm if there’s a known regression or changed behavior for Google Sheets values reads in the CLI/API?

Hi there, Thanks for the detailed write-up, that repro is really helpful. The single-cell read working while a two-cell read on the same row times out is the key clue here: on our side those calls are built and sent to Google identically, so the column count alone shouldn't change anything, and the fact that a plain

composio proxy

to the values endpoint also hangs tells me this isn't a CLI-only thing or your OAuth (which all lines up with your other Google tools working). So this looks like something on our side, not your Google account. I don't want to hand you a wrong fix, so before I dig in, could you share a few things from one failing run: • The connected account ID (or the Google email) you're using • The

spreadsheet_id

and the exact range • A rough UTC timestamp of the failing call, plus any request ID the CLI prints With those I can pull the execution logs and trace where it's stalling. In the meantime, single-cell

GOOGLESHEETS_VALUES_GET

reads are still going through if you need a stopgap for the header lookups. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.