[n8n Issue] Google Drive Trigger stuck in infinite loop (Fetch Test Event) after updating to v2.1.4
afluisaude
PROOP

3 months ago

Hi support team,

I am experiencing an execution issue in my n8n environment (version 2.1.4) hosted on Railway.

The Issue: When configuring the Google Drive Trigger node, I use the Fetch Test Event feature and upload a new file to the monitored folder. The node remains stuck in a "loading" state (infinite loop) and fails to capture the event.

Deploy Logs (Railway): The following error appears repeatedly in the logs: TypeError: Cannot read properties of undefined (reading 'execute')

Workflow Context:

  • Trigger: Google Drive Trigger (File Created).

  • Sequence: Wait Node (15s) -> Switch Node (checking fileExtension).

  • Observations: The error persists even when files are present in the folder. It seems like a failure in passing binary properties or metadata from the Trigger to subsequent nodes in this specific version.

Could you please verify if there are any resource limits or network configurations on Railway that might be blocking the Google Drive Webhook/Polling in this n8n version?

Best regards,

$10 Bounty

1 Replies

Hi there,

Your service should be able to handle webhooks and polling without any platform-level restrictions. The error you're seeing (TypeError: Cannot read properties of undefined (reading 'execute')) is coming from n8n itself, not from Railway.


Status changed to Awaiting User Response Railway 3 months ago


Loading...