Bug Description

If a Google Drive Download File node fails with "Continue on error using error output" enabled, the workflow silently stops successfully instead of running the error branch.

The error could be reproduced with an image for which n8n doesn't have permission. The expected error is: "The resource you are requesting could not be found" (when I don't set "continue on error" option)

I managed to workaround it using "Always output data" which will make the next node to fail (as expected).

To Reproduce

1. Add Google Drive Download File Node
2. Put a Google Drive Image link for which n8n doesn't have permissions to access
3. Set settings to "On error -> Continue (using error output")
4. Connect "Error" output to a Node

Expected behavior

I expect the Node, connected to the error output to be executed. However, it looks like the Google Drive node fails silently and doesn't pass the error. The workflow just stops successfully.

Debug Info

Debug info

core

• n8nVersion: 2.9.4
• platform: docker (cloud)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: enterprise (sandbox)
• consumerId: 00000000-0000-0000-0000-000000000000

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/145.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-03-20T07:39:43.949Z

Operating System

n8n cloud

n8n Version

2.9.4

Node.js Version

24.13.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud