Google Drive file upload stopping after the first item

[Chaoscontrol]

Describe the problem/error/question

Trying to create a basic flow to backup all my workflows to Google Drive.
Everything works, and it creates the json file with the correct content in the right folder, but it only does for the first item. Then it fails with this error.

What is the error message (if any)?

ERROR: The resource you are requesting could not be found

File not found: 1r7OyonkYzciI0ti-MDEOJqSmegk3JkZu.

Error 404 NodeApiError: The resource you are requesting could not be found

Please share your workflow

Share the output returned by the last node

Can’t because it’s too long, but basically it’s the plain output from n8n node. A list of all my workflows.

Information on your n8n setup

• n8n version: 0.221.2
• Database (default: SQLite): MariaDB
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): HomeAsisstant OS
• Operating system:

[MutedJam]

Hi @Chaoscontrol, I am just testing this on my end, but am already seeing several different files showing up in Google Drive while the workflow is still running:

Is there a chance your Google Drive account has simply hit some limit and Google doesn’t allow any more uploads?

[Chaoscontrol]

I honestly can’t think so. The Shared drive is mostly empty, and the files are ridiculously small. And it always fail after the first one (I only have 6 workflows too, so it wouldn’t be that much…).

Also from the error given it seems when it’s generating the second file with its ID or name, it’s when the issue happens. But don’t know why. Really weird that it works for you! :S

You didn’t change anything right? Maybe I should be using a different credential?

Edit: I was using a Service Account credential and have now tried with OAuth 2, but no difference.

HOWEVER, I have changed the destination folder to a random folder in My Drive (instead of in my Shared Drive) and it worked perfect. So might indeed be either some restriction on the SD, or some limitation in that case. Will continue testing.

Edit 2:
Tested splitting in batches of 1 to try and add a delay and that way go over the limit, but it didn’t work. The error happens with a single item, although the file is created successfully in the folder, which is weird. :S

[MutedJam]

HOWEVER, I have changed the destination folder to a random folder in My Drive (instead of in my Shared Drive) and it worked perfect. So might indeed be either some restriction on the SD, or some limitation in that case. Will continue testing.

Oh, to be honest I missed the shared drive part at first. I only tested this with one of my own folders.

Shared Drives are unfortunately not fully supported by n8n, so you might want to leave a vote on the respective feature request (and possibly add a comment that you’re using the regular Google Drive node here, as the conversation on that requests seems to be mostly about the trigger node).

[Chaoscontrol]

Ok, just did.

I am testing now and I tried disabling the “Resolve data” toggle in the node and then the error doesn’t happen. Will keep testing and reporting back.

Edit:

So yeah, since this workflow doesn’t need to output any more data, I can keep the Resolve data toggle deactivated. Then there’s no error and it works all good without issue.

Here’s the fully working flow. I think I will create a template from this, even if it’s basic, I think it’s pretty useful and the existing similar template is outdated.