Google Drive Trigger Node not being able to fetch test data on versions 1.92.0 and above

[Axioma]

This is a bug report regarding the Google Drive Trigger node.

When using the “Fetch Test Event” button on the Google Drive Trigger node, it is unable to find any data on n8n versions 1.92.0 and newer. The issue seems to affect all “Watch For” events (such as Watch Folder Updated, File Created, File Uploaded, etc.) when the trigger is configured to monitor a specific folder.

This functionality works perfectly on version 1.91.2. I have tested multiple versions and can confirm that 1.91.2 is the last version where fetching test events works as expected. On all subsequent versions I’ve tested, the node fails to retrieve data for the test run, regardless of the chosen watch event.

The issue appears to be a regression introduced in version 1.92.0. I had to downgrade my instance to 1.91.2 to keep my workflows functional.

• Image 1 (The Issue): On newer versions, the node executes but returns “No Google Drive data found”, even when there are recent changes in the folder that match the trigger event. (Você precisará fazer o upload da imagem para um serviço como o Imgur e colar o link aqui)
• Image 2 (Working correctly): On version 1.91.2, the node successfully fetches the data for the same folder and trigger configuration.

What is the error message (if any)?

There is no explicit error message. The node simply completes the test execution with the message: No Google Drive data found. We didn't find any data in Google Drive to simulate an event. Please create one in Google Drive and try again.

This happens despite the fact that the target folder has been recently modified in a way that should trigger the event (e.g., a file was updated, added, etc.).

Information on your n8n setup

• n8n version: The issue occurs on 1.92.0 and newer versions. I have downgraded to 1.91.2 as a workaround.
• Database (default: SQLite): Default (SQLite).
• n8n EXECUTIONS_PROCESS setting (default: own, main): main (default setting).
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker (using Easypanel).
• Operating system: n8n is running inside a Docker container.

[xratios]

Hi there, I faced the same issue. However, it worked perfectly when I clicked “execute workflow” for my Google Drive Trigger Node instead of “Fetch Test Event”.

[James_Boadi]

Yes this is a bug that needs to be fixed by the developers. Happens locally when running inside docker. I initially suspected it was caused by google not recieivng the event because of the webhook configuration.

[Nayel99]

I refreshed the OAuth connection and it worked!