Google Drive download errors now route to error output
The Google Drive node's "Continue on error" option now works for file downloads, routing failures to the error output instead of silently stopping workflows.
When workflows encountered permission denied or missing file errors during Google Drive downloads, nodes configured with "Continue on error" would stop silently rather than routing to the error output branch. Users expecting their error handling flows to execute were left with completed workflows and no data.
File downloads in the Google Drive node now route errors through the same error handling path as other operations. When a download fails, the error message reaches the configured error output, allowing workflows to recover, log failures, or trigger alerts as intended.
This fix addresses the download operation for the file resource in the Google Drive V2 node, where the error handling logic diverged from the rest of the node's operations since the V2 overhaul. A test workflow verifies the correct behavior.
View Original GitHub Description
Summary
<!-- Describe what the PR does and how to test. Photos and videos are recommended. -->V2 of Google Drive node for some reason didn't properly handle this.continueOnFail() if the operation is download and resource is file. It was like this since the original overhaul PR, so it is not clear why it was done this way. But it means that if the node errors when downloading a file and continue on error is enabled - the node outputs nothing. This PR fixes that and makes sure that all operations are handled on error
Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->https://linear.app/n8n/issue/NODE-4712/community-issue-google-drive-download-file-node-doesnt-continue-on Closes #27312
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported) - I have seen this code, I have run this code, and I take responsibility for this code.