Why Has the Google Drive Trigger Stopped Monitoring New Files in the Workflow?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

We have a workflow that uses a Google Drive trigger monitoring a folder for newly added files. As of 7:37pm MST this evening, it has stopped. Several new files have been added since, but no events have been emitted by the Source

2

I too wish that Google would more reliably emit events…

These issues are very frustrating. :disappointed:

3

Try re-creating the source perhaps?

4

I’ve enabled PD access to the WF if needed: 404: Not Found - Pipedream

5

It’s worked fine up until tonight. If I need to constantly remove / recreate the Source, that won’t work for production.

6

Best way to get PD support is probably to create a support ticket.

7

I’ll do that as well

8

Yep, I see it in our support tickets, thanks!

9

Much appreciated. This one is a blocker and our folder is filling up with unprocessed files, so anything to expedite would be :pray: greatly appreciated!

10

I see a potential issue, not entirely confident. Will push a change to the source code

11

[Google Drive] Generate a new channelID when renewing subscription — PR — published!

12

Could you please create a new trigger in your workflow since triggers cannot be updated like actions

13

Yes. 1 moment.

14

Done

15

Awesome thanks. The new trigger should renew the subscription with a new channel ID from now on. Previously, it was using the same channel ID and that may caused some conflicts

16

ok I am watching the source…still idle.

17

Can you try uploading a new file

18

I did. I just uploaded 2.

19

Oh sorry, the old trigger should be in a dead state

20

oh.