This topic was automatically generated from Slack. You can find the original thread here.
Hi. My google sheet new row added trigger stop working all of sudden. From logs last attempt to read new row was from 2 hours ago. can please help. havent changed anything
Hi , in order to get more context into your workflow, would you mind submitting a ticket on Support - Pipedream?
Is this affecting all users? It appears that we are also not getting “new row added” updates since yesterday
We are affected as well.
We’re not receiving any updates at all.
No new or updated file events, etc.
: Should everyone be creating tickets for this?
Yesterday there was this log in the Google Drive source:
Stopped push notifications on channel ...
Notifications for resource ... are expiring at 1720782047000. Stopping existing sub
Meaning there will be no more notifications at 7AM this morning.
We even tried creating another source with the same parameters but the same log appeared:
T12:02:15
log
Stopped push notifications on channel ...
Notifications for resource ... are expiring at 1720886530000. Stopping existing sub
It expired the exact time it was created…
Looks like it could be some issue with Google’s webhooks if different users were affected without changing anything
The channel subscription has to be renewed after 24 hours, this is enforced by Google
But it seems that the new channel subscription was not activated?
@U05LWJMUX0A Can you share the trigger ID so I can take a look?
Yes, Where I can find the trigger ID?
Also, I just created a new workflow and the same type of trigger is working properly. As you mentioned, maybe it’s a problem affecting only existing workflows and triggers 
The channel was renewed successfully at June 11th 20:34 GMT, but stopped receiving updates since then
Did all your Google Sheets triggers also stop emitting events?
Yep! About three workflows
I just tried something in a different workflow and it’s probably a helpful tip for others:
• Completely remove the original trigger from your workflow
• Add a new trigger of the same type
• Save and continue, it should successfully load your events
Just need to keep an eye if it’s gonna “renew” properly from now on
, you recently worked on some of the Google Drive usability updates, but looking at the code I don’t see that you touched anything related to webhook creation or renewal.
Wondering if you have any ideas as to why this bug might be happening?
I’m looking into this as well.
Got it, were these three triggers created roughly at the same time?
I don’t think so… Two were created a couple of weeks ago and one is a WIP right now.
But they all use the same “Account”, so that can be a cause…
Gotcha, I ask this because this was an ongoing issue (the triggers suddenly stopped emitting after some time)