Google Drive New/Modified file Trigger not running in Production Mode

Bugs & Issues
1

Hi,
I’ve been trying to run a workflow for invoice processing which detects new pdf files in a google drive folder and downloads them for processing through amazon s3 and textract for data extraction to google sheets. It seems to have been working well in April 2025 when I tested the workflow in production (deployed) mode and test mode (scenario/ individual nodes). Authorization was google oauth2
However as of May 2025, it does not detect new files in my google drive folder even after waiting for trigger intervals (account currently is micro subscription).
On running scenario once (test your scenario), I get the following error :

workflow
workflow1920×1080 326 KB

newmodifiedtrigger
newmodifiedtrigger601×843 55.3 KB

Running individual nodes from beginning to end works normal however.
I have tried the workflow with google oauth2 and personal app Oauth (setup using latenode documentation) but no difference. I have tried other scenarios with the new file trigger but I am having the same problem (no triggering in production mode). It works perfectly well in my make scenarios and zapier so I am sure it is not the issue with authorization.

Has anyone encountered a similar issue with google new/modified file trigger node? Would appreciate the help on this.

2

Hi! That’s definitely unusual behavior. Tomorrow, we’ll test the functionality of Google Drive triggers in all modes and plan fixes if we find any issues.

I’ll get back to you with an update (and hopefully a quick solution) in the first half of the day.

3

@Raian . Thanks. I appreciate it. No rush. I was able to use the alternative of a latenode webhook trigger using a google apps script looking for new files in my drive folder. It is working perfectly fine in production mode with that for now but would be great to see the native node option in the future.