This topic was automatically generated from Slack. You can find the original thread here.
Hello guys,
I have built a pretty big (complex) flow, and my (google drive) trigger stopped wortking for some reason?
Anyone els have this issue? Can it be related to memory or time settings on the flow?
If you are running into timeouts or OOM (out of memory) issues, it’s not related to the trigger.
It’s just a UI issue with Pipedream being currently unable to display which step actually failed (they are working on a fix).
Solution: increase timeout or add more memory.
ok, yeah I dont get any error message, just thtat the drive does not react on new files added. I have removed, added reconnected and all other things i can do - still dead
Under the “Sources” tab in the dashboard you should be able to find your Google Drive source that triggers the workflow.
There’s a Logs section within the source, it might give more details on why it’s not triggering as you expect.
Are you using My Drive or a Shared Drive?
We’ve experienced issues with Shared Drives in the past.
I am using My drive.
And my developer now changed to his account on google drive, and it work on his account.
Feels soo depressing, spend 1000usd+ to build the workflow, and everything is working except the simple trigger… Such a disapointment
Pipedream isn’t really responsible for how Google decides to send events though. :man-shrugging:
One things we’ve noticed in the past is that it works better when the trigger is associated with the account who owns the files.
Otherwise, the events can be delayed by as much as 30 minutes, or even never arrive. :man-facepalming:
That might be why Zapier’s integration works with regular polling instead of with events. 
Well, that I understand, but if I know that a “simple” storage bug would and the first step might be an issue I would have reconsiderd subscribing and spending 2 weeks and 1k on “testing it”.
Is there any support I can hire to look into this issue or what would the next step be here?
I guess I need to report this as a bug in “Bug channel?
Idk if that will make a big difference.
Yeah, maybe you are right. Ill wait and see if anyone help me.
I will also try to start a new Google drive account and setup and copy all steps into a new flow.
Thanks for responding anyway
I created a new Google Drive account and now its working with no issues :S
Glad to hear recreating the Google Drive source fixed the issue for you.
Recreating sources pulls in the latest version of the source’s code, which might have included a fix for the issue, or potentially the webhooks that power this source were accidentally removed from within your Google Workspace.
In the future, we highly recommend reporting bugs within our support ticket system: Support - Pipedream
Posted thread to Discourse: Why Has My Complex Flow's Google Drive Trigger Stopped Working: Could It Be Related to Memory or Time Settings?
Now I got the same issue again with the “new” google drive… This is a very weak spot for pipedream.
Sorry to hear that, have you opened a support ticket for this issue?