My google credentials keep disconnecting

Describe the problem/error/question

I have had my n8n self hosted instance in railway for about 3 months, it had been working perfectly to connect to google suite with Oauth2.0 credentials, but since monday september 8, 2025 (when google had an outage) I have been having the problem that my credentials keep disconnecting. I enter the workflow connect them again and they work for about 2 hours and disconnect again. This has been happening for the last week, I created a service account to see if connecting with service account fixed the problem, but thye still keep disconnecting every couple of hours. I need to fix this because my automations are not working properly I have to enter and connect every couple of hours.

What is the error message (if any)?

Your request is invalid or could not be processed by the service

column 9827483463398fbb7d6b96916fe451d8bdefa0e8.role does not exist

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

<!{
“errorMessage”: “Your request is invalid or could not be processed by the service”,
“errorDescription”: “column 9827483463398fbb7d6b96916fe451d8bdefa0e8.role does not exist”,
“errorDetails”: {
“rawErrorMessage”: [
“column 9827483463398fbb7d6b96916fe451d8bdefa0e8.role does not exist”
],
“httpCode”: “42703”
},
“n8nDetails”: {
“nodeName”: “Read Cubbo Orders1”,
“nodeType”: “n8n-nodes-base.googleSheets”,
“nodeVersion”: 4.6,
“resource”: “sheet”,
“operation”: “read”,
“time”: “13/9/2025, 9:00:55 a. m.”,
“n8nVersion”: “1.110.1 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: Your request is invalid or could not be processed by the service”,
" at ExecuteContext.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Google/Sheet/v2/transport/index.ts:78:9)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at GoogleSheet.spreadsheetGetSheet (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Google/Sheet/v2/helpers/GoogleSheet.ts:129:21)“,
" at ExecuteContext.router (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Google/Sheet/v2/actions/router.ts:43:20)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Google/Sheet/v2/GoogleSheetsV2.node.ts:30:10)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1185:9)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1534:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2098:11"
]
}
}>

Information on your n8n setup

  • n8n version: 1.110.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): railway instance docker
  • Operating system:

Which google nodes are you using? Some of them can use a service account over oauth which will allow for a more permanent auth.

I am using gmail and google sheets, but what is really weird is that this behaviour started on monday september 8 before that the Oauth2.0 did not had this error and I did not have to reconnected every couple of hours. This is the real issue I want to fix, why it worked well before and now it does not

if you would be available for a short call so that you can help me trouble shoot it would be great, I currently manage my small company’s operation with n8n and I am willing to pay some money to get this fixed

Not sure what is happening on Google side, but Id recommend switching to service account if it is available as oauth will always have some sort of an expiry on it

I have changed to service account since friday 12 of september but over the weekend it still kept failing.

You are not alone:

1 Like

Thank you man the solution was in that thread , you just have to redeploy both the primary and workers in railway

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.