user-1
July 20, 2024, 1:33am
21
But the last patch was pushed on April 26th and this is the first time someone is reporting this issue again
user-1
July 20, 2024, 1:33am
22
Andrew I see you pushed this PR in April related to how we renew subscriptions, can you share a little bit about how this worked before and then after?
PipedreamHQ:master ← PipedreamHQ:fix-google-drive-subscription-renewal
opened 04:19PM - 18 Apr 24 UTC
Whenever a subscription was being renewed, the same `channelID` was given to the… Google SDK for the new Channel ID.
[Google's docs](https://developers.google.com/drive/api/guides/push#renew-notification-channels) indicate the opposite:
> As always, you must use a unique value for the id property of the new channel
This fix ensures a new `channelID` is given when requesting a new subscription (and correctly stops the previous `channelID` subscription).
user-1
July 20, 2024, 1:33am
23
Yes, this is what I was talking about
user-1
July 20, 2024, 1:33am
24
Before the patch, we were using the same channel ID when renewing the channel subscription
user-1
July 20, 2024, 1:33am
25
After the patch, we started generating a new channel ID every time the subscription renewed
user-1
July 20, 2024, 1:33am
26
So it turns out that this was a Google outage, actually.
It seems to be recovering now though, so everything should be back to normal soon!