Occasionally the Google Drive trigger will error with very weird timing info

Questions
,
1

Describe the problem/error/question

Every week or so, my Google Drive trigger will error with a generic “AxiosError: Request failed with status code 500”. However, the weird part is the “Started” field is “Starting Soon” and the “Run Time” field is a huge value like “29131801:11m”.

The result I’d like is for this 500 error never to occur, but I think that issue is on the Google side. So, my backup result I’d like is if this execution shows up normally, with a start time and short run time like 1ms. This is because the weird run time causes problems with the execution list display. I have to delete them to restore the list. (Which is why there’s no screenshot with this post. Next time it happens, I’ll take one and add it here.)

What is the error message (if any)?

{ “message”: “500 - {"error":{"code":500,"message":"Internal Error","errors":[{"message":"Internal Error","domain":"global","reason":"internalError"}]}}”, “name”: “AxiosError”, “stack”: “AxiosError: Request failed with status code 500\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:19:12)\n at Unzip.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:599:11)\n at Unzip.emit (node:events:536:35)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at processTicksAndRejections (node:internal/process/task_queues:82:21)\n at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:45:41)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at invokeAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:173:16)\n at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:513:26)\n at Object.request (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1145:50)\n at PollContext.requestOAuth2 (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:792:12)\n at PollContext.requestOAuth2 (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1153:20)\n at PollContext.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Drive/v1/GenericFunctions.js:55:14)\n at PollContext.googleApiRequestAllItems (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Drive/v1/GenericFunctions.js:70:20)\n at PollContext.poll (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Drive/GoogleDriveTrigger.node.js:491:15)”, “code”: “ERR_BAD_RESPONSE”, “status”: 500 }

Please share your workflow

Share the output returned by the last node

None

Information on your n8n setup

  • n8n version: 1.91.3
  • Database (default: SQLite): PostgresQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Container in AWS ECS
  • Operating system: Ubuntu?
1 Like
2

It seems like a network issue, and tbh, its a trigger so it’s likely not processed anything and will try again, its slightly odd with the runtime, but that could be it just stuck be interesting to know further

3

With a recent upgrade to version 1.94.1, this problem has morphed into something else.

Now it is impossible to use the Google Drive Trigger configured to watch a file (as opposed to a folder). I had one workflow with this trigger configured like this and it caused my Google Drive API usage to spike to 1/s and the n8n container to quickly use up all available memory. My only solution was to replace this trigger with a scheduled trigger that I run daily. This is not ideal as I would rather the workflow trigger when the file in question is updated.

Another observation that someone odd is going on is that saving or activating this workflow always timed out with a 504 error. I think that’s because the polling was happening as fast as possible, but I could be wrong.

I know this is missing all the usual context that is in the original template, but since I have a workaround I’m not really committed to finding a solution. Something about how n8n “watches” a file in the Google Drive is broken as it’s really polling (with 200 responses) every 1 second or maybe as fast as it can.

If you are having the problem described and need it to be solved, I suggest creating a new post with all of the supporting info.

Thanks,
Eric