Fixed
Status Update
No update yet.
Comments
ri...@gmail.com
This is the full error message:
{
"error": {
"errors": [
{
"domain": "push",
"reason": "channelUnknown",
"message": "WEB_HOOK channel unavailable for: {address=<target_url>}"
}
],
"code": 400,
"message": "WEB_HOOK channel unavailable for: {address=<target_url>}"
}
}
{
"error": {
"errors": [
{
"domain": "push",
"reason": "channelUnknown",
"message": "WEB_HOOK channel unavailable for: {address=<target_url>}"
}
],
"code": 400,
"message": "WEB_HOOK channel unavailable for: {address=<target_url>}"
}
}
dv...@gmail.com
Faced the same issue. However, it works for some URLs I have. But, they have all the same setting of ssl and other stuff as the ones that don't work.
[Deleted User] <[Deleted User]>
Can you describe the differences (host, path, etc) of the URLs that work vs don't work?
ad...@highfive.com
We are also seeing the same error for the events.watch API call. This is happening for all of our channels; again despite no changes made on our end. These errors ramped up over the past 24 hours or so, but at about 11:00UTC today 100% of calls to events.watch started failing.
[Deleted User] <[Deleted User]>
Same thing for us.
[Deleted User] <[Deleted User]>
I'm receiving the same error and my webhook target is also available. The first occurrence logged is near 9 hours ago.
br...@robinpowered.com
Also having this issue. We've changed nothing on our end. We first noticed a small amount of these on the 16th. From the 16th-18th it occurred more and more, but still not too much. Then starting this morning we noticed it happening boatloads.
ty...@tylerbainbridge.com
We're experiencing this too-- all calls to events.watch have failed since 12AM EST.
No changes to our code.
No changes to our code.
br...@conduithq.com
We're experiencing this and it's impacting a large portion of our users. Calls to `event.watch` are failing since around midnight ET.
[Deleted User] <[Deleted User]>
We have begun to see partial recovery at 15:23 PDT (22:53 UTC).
fr...@serioplast.com
I'm receiving the same error at 3.30 CEST
le...@doist.com
We experienced the same pattern; occasional failures the previous couple of days, and since a few hours ago it always fails, and affects many of our users.
[Deleted User] <[Deleted User]>
I'm receiving the same error too. Any information about Google Team?
In my case, I'm watching folderId.
In my case, I'm watching folderId.
[Deleted User] <[Deleted User]>
We are also facing same problem. Calls are failing randomly.
da...@gmail.com
Same problem here.
ma...@gmail.com
I have the same error.
ca...@gmail.com
I'm facing the same problem.
da...@gmail.com
I'm seeing this same problem as well. This feature has been running and working fine in production for months, then yesterday morning it started failing 100% of the time.
lu...@google.com
Thank you for reporting the issue! We are currently working on addressing it.
al...@workato.com
Same here
ey...@meekan.com
From internal case comments:
"
There's no workaround available at this time. However, our engineering team has identified the root cause and is actively working to resolve the issue. A fix is currently being rolled out but it may take up to 2 days to propagate to all users.
"
Brace yourselves.
"
There's no workaround available at this time. However, our engineering team has identified the root cause and is actively working to resolve the issue. A fix is currently being rolled out but it may take up to 2 days to propagate to all users.
"
Brace yourselves.
br...@robinpowered.com
This morning we're already seeing substantially less errors than the same time yesterday. So it seems like some good progress has been made.
br...@conduithq.com
Google's message from #22 looks concerning, but over 95% of our webhooks have recovered successfully and no longer erroring out:
https://twitter.com/bradr/status/1009448722391027712
[Deleted User] <[Deleted User]>
We see complete recovery at 07:35 PDT.
ma...@gmail.com
From google
[Fully resolved] Our engineering team indicates that the issue with the Google Calendar API events.watch method should now be resolved for all affected users. We thank you for your patience while we've worked on resolving the issue.
[Fully resolved] Our engineering team indicates that the issue with the Google Calendar API events.watch method should now be resolved for all affected users. We thank you for your patience while we've worked on resolving the issue.
Description
Since about 2:50am UTC our app has been receiving response 400 for channel.register calls for users in all domains.
The response includes "WEB_HOOK channel unavailable for <target_url>" and our webhook target is available, as it has been for the last 2-3 years. There were no changes in production environment.
The only other reference to this error message is the following SO thread:
What is the expected output? What do you see instead? If you see error messages, please provide them.
Since the target_url is available, and same code has been running for the same users for the last few years, we expected a 200 OK response as usual.