Assigned
Status Update
No update yet.
Comments
bl...@google.com
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191602.
jp...@google.com
I have reported this to the engineering team and future updates will be shared here. Thank you for your patience.
ma...@futurenet.com
Yesterday again we stopped receiving push notifications at 11:10am on our topic, and they didn't resume until the watch was refreshed at 5am today. Between these times we have had emails coming into the inbox.
ma...@futurenet.com
At 2024-07-06 00:00:04.902 BST we received the following response from the gmail watch command:
message: {
expiration: "1720825204889"
historyId: "8923270"
}}
The expiration here corresponds to Saturday, 13 July 2024 00:00:04.889 GMT+01:00 DST
This is an expiration of 1 week in the future, which is expected from the documentation.
Later that day we have an email come in at 6 Jul 2024, 16:02pm, however by then it appears that pubsub notifications to the topic have stopped, this can be seen in the screenshot of the publish requests chart on that topic.
There are no publish requests at the time of the incoming email, this doesn't align with the expected behaviour right?
message: {
expiration: "1720825204889"
historyId: "8923270"
}}
The expiration here corresponds to Saturday, 13 July 2024 00:00:04.889 GMT+01:00 DST
This is an expiration of 1 week in the future, which is expected from the documentation.
Later that day we have an email come in at 6 Jul 2024, 16:02pm, however by then it appears that pubsub notifications to the topic have stopped, this can be seen in the screenshot of the publish requests chart on that topic.
There are no publish requests at the time of the incoming email, this doesn't align with the expected behaviour right?
ma...@futurenet.com
Also, in the interest of confirming expected behaviour, sometimes we see outputs from our system that suggests duplicated push notifications occurring, usually in quick succession but not necessarily always.
For example yesterday we have 6 events generated from one incoming email, but usually it is just one or two.
Can I confirm that this can happen and doesn't represent a situation where something is misconfigured?
Thanks.
For example yesterday we have 6 events generated from one incoming email, but usually it is just one or two.
Can I confirm that this can happen and doesn't represent a situation where something is misconfigured?
Thanks.
jp...@google.com
Can you share a "sync" message that was sent to your endpoint? This should occur soon after the watch was created.
ma...@futurenet.com
I'm not entirely sure these are being received.
To clarify, should I expect a pub/sub message on the configured topic after creating a watch?
That is what I would expect reading the following documentation:https://developers.google.com/gmail/api/guides/push#watch_response
However I have a cloud function running that is printing out the data of messages from the pub/sub topic, and it doesn't print out anything when a new watch is created.
It does however print out the expected response when the inbox receives a new email e.g.
b'{"emailAddress":"email@address.com","historyId":8938908}'
Am I looking in the right place?
To clarify, should I expect a pub/sub message on the configured topic after creating a watch?
That is what I would expect reading the following documentation:
However I have a cloud function running that is printing out the data of messages from the pub/sub topic, and it doesn't print out anything when a new watch is created.
It does however print out the expected response when the inbox receives a new email e.g.
b'{"emailAddress":"email@address.com","historyId":8938908}'
Am I looking in the right place?
jp...@google.com
Whoops, sorry got this mistaken with the behavior behind another issue related to watch expiration in the Admin Reports API,
ma...@futurenet.com
Ah okay no problem, so does my set-up here sound correct to you, nothing you can think of that I might be missing here?
If there's anything else for me to try or info to provide just let me know and I'll try my best!
If there's anything else for me to try or info to provide just let me know and I'll try my best!
ma...@futurenet.com
Hi were there any updates from the engineering team or elsewhere?
ma...@futurenet.com
Hello, this happened again on the 3rd of August, we didn't receive a pub/sub notification for an email containing a business report, this caused us to miss the processing of that report, which is affecting other users in our business.
Are there any updates? It's been nearly two months since this was first reported to the engineering team!
Are there any updates? It's been nearly two months since this was first reported to the engineering team!
Description
Before opening a new issue, please
+1to vote.Similar to
Description
Last week we stopped receiving mailbox push notifications on our Pub/Sub topic, this week it has happened again.
Code
The following code is used to set up the watch
Output
Watch request is successful giving the following output:
Steps
This watch is refreshed everyday at 5am so there should never be any downtime. However we can see emails coming in, with no corresponding Pub/Sub messages