Google Sheets Tag – Persistent 400 Server Error on auth-proxy

Dear Stape Community,

We are experiencing a persistent issue with the Google Sheets tag in our server-side GTM container. Despite multiple attempts to fix it, every request ends with a 400 Bad Request (Server error).

What we have already tried:

  • Full Reconnection: We have performed a complete hard reset of the Google Sheets Power-up, including revoking permissions in the Google Account security settings and re-authorizing.
  • Isolated Test: We created a brand new spreadsheet with a simple name (“Test”) and tried to send only a single string value to a single column.
  • Ownership Check: The spreadsheet owner is the same email address used for the Stape Google Sheets connection.
  • Permissions: We ensured all necessary OAuth scopes were checked during the authorization process.

Request Body (minimalistic test):

{
  "spreadsheetId": "193QgB7ODXs4hKhpH8Y1UZ62R18tRMB859OPB3F90mKI",
  "range": "'Test'!A2:A",
  "type": "add",
  "values": [["ae8df37ctalwmn336cb747c0f6a16070af"]]
}

Response Body:

{
  "body": {
    "message": "Server error"
  },
  "error": {
    "code": 400,
    "message": "Server error",
    "description": "Server error"
  }
}

The setup worked perfectly until recently. It seems the issue lies within the auth-proxy communication between Stape and Google API, as even the most basic requests are failing.

Hey @Patrik_Roob thanks for flagging this. Could you advise when this started happening?

Also can I get your Stape container id please?

Hello Dan,

The error began to appear on February 12, 2026.
Stape container id: obwbugcx

Thanks, investigating

@Patrik_Roob please try again, should be OK now - we’ve located some issues our end.