Send a test push notification. Error Code: GatewayTimeout

Question

Send a test push notification. Error Code: GatewayTimeout

Baha Masoud 41

I had my notification client registered and was able to send notifications normally, suddenly, I tried again and I am getting this all the time (tried many times over 4 hours period):

Error code: GatewayTimeout
Message: The gateway did not receive a response from 'Microsoft.NotificationHubs' within the specified time period.

I tried to send from the portal, VS2k19, and the console, nothing has arrived.

What is the possible problem?

brtrach-MSFT 7,386 Reputation points Microsoft Employee

2020-11-27T19:31:33.037+00:00

We have asked this customer to reach out to us offline. If you have this error as well or a solution to suggest, please continue the discussion on here.
Jorge Garcell 11 Reputation points

2020-11-28T23:00:00.68+00:00

Same problem here, using Visual Studio 2019 and developing an Android App on Xamarin. Android target Frame 10.0 (Q).
Mike Hong 16 Reputation points

2020-11-29T17:30:52.82+00:00

Also having the same issue after following the instructions for this tutorial.
sadomovalex 3,601 Reputation points

2020-11-30T15:17:05.08+00:00

does it happen in one specific notification hub? I.e. if try to create new notification hub and send test push notification from there - will it still happen?
jg-dcap 11 Reputation points

2020-11-30T15:45:45.56+00:00

I'm getting it when using azure portal test send on an existing notification hub and also one I just created.
Mike Hong 16 Reputation points

2020-11-30T16:40:05.59+00:00

Yes I tried creating a new notification hub and got the same error again.
dsav 16 Reputation points

2020-11-30T17:20:20.12+00:00

Ran into the same problem over the weekend. At some point in the last couple of days, push notifications started failing in two different notification hubs. The error is the same - always a 60 second timeout.

Interestingly, I also tested this in a test environment where my Apple developer account is expired and I got an immediate response back saying the credentials are bad. Trying an android message in that environment results in the same timeout error as my other two environments.

The notifications fail from my app, visual studio's test tool and the test tool in the azure portal.
Johny B 21 Reputation points

2020-11-30T19:22:51.97+00:00

I also have the same problem and its extremely annoying with little to no information online... :(
brtrach-MSFT 7,386 Reputation points Microsoft Employee

2020-11-30T19:35:15.68+00:00

Thank you for sharing this with us and we apologize for the frustration you have encountered. We have reached out internally to see if this is a known issue and what the next steps are. Once we have an update to share, we'll post it here.
brtrach 246 Reputation points

2020-11-30T22:33:26.12+00:00

Just wanted to provide a quick update that the product group is investigating these errors right now. We will share more update as we receive them.
Tim Gregor 1 Reputation point

2020-12-01T00:13:16.577+00:00

Same issue here. Was able to verify APNS using Pusher so it appears certs and app are working properly.
Johny B 21 Reputation points

2020-12-01T17:04:32.14+00:00

This is making me question our decision to go with Azure Notification Hub. The SLA for paid subscription is 99.9% yet it has not worked for 4 days now. If this is a system wide issue, why isn't there any outage details anywhere?
Jon Nichols 1 Reputation point

2020-12-01T17:55:40.26+00:00

We are also experiencing this issue with a brand new notification HUB
Jon Nichols 1 Reputation point

2020-12-01T18:06:08.61+00:00

I've also created a brand new notification Hub, added my server key for Google, Hit test send, got this same error. I am however able to send push notifications in Firebase.
Johny B 21 Reputation points

2020-12-01T18:40:12.727+00:00

I even created a brand new subscription under a new account - still no go. This seems to be a system wide issue yet there's not much noise around it.... makes me wonder how well is this product supported... we're in the middle of migrating from appcenter.
Ehrlish, Robert 1 Reputation point

2020-12-01T22:46:54.607+00:00

Same problem. Been messing with this for days and just found this post..

Hopefully the problem can be resoled soon

brtrach-MSFT 7,386 Reputation points Microsoft Employee

2020-11-27T19:31:33.037+00:00

We have asked this customer to reach out to us offline. If you have this error as well or a solution to suggest, please continue the discussion on here.
Jorge Garcell 11 Reputation points

2020-11-28T23:00:00.68+00:00

Same problem here, using Visual Studio 2019 and developing an Android App on Xamarin. Android target Frame 10.0 (Q).
Mike Hong 16 Reputation points

2020-11-29T17:30:52.82+00:00

Also having the same issue after following the instructions for this tutorial.
sadomovalex 3,601 Reputation points

2020-11-30T15:17:05.08+00:00

does it happen in one specific notification hub? I.e. if try to create new notification hub and send test push notification from there - will it still happen?
jg-dcap 11 Reputation points

2020-11-30T15:45:45.56+00:00

I'm getting it when using azure portal test send on an existing notification hub and also one I just created.
Mike Hong 16 Reputation points

2020-11-30T16:40:05.59+00:00

Yes I tried creating a new notification hub and got the same error again.
dsav 16 Reputation points

2020-11-30T17:20:20.12+00:00

Ran into the same problem over the weekend. At some point in the last couple of days, push notifications started failing in two different notification hubs. The error is the same - always a 60 second timeout.

Interestingly, I also tested this in a test environment where my Apple developer account is expired and I got an immediate response back saying the credentials are bad. Trying an android message in that environment results in the same timeout error as my other two environments.

The notifications fail from my app, visual studio's test tool and the test tool in the azure portal.
Johny B 21 Reputation points

2020-11-30T19:22:51.97+00:00

I also have the same problem and its extremely annoying with little to no information online... :(
brtrach-MSFT 7,386 Reputation points Microsoft Employee

2020-11-30T19:35:15.68+00:00

Thank you for sharing this with us and we apologize for the frustration you have encountered. We have reached out internally to see if this is a known issue and what the next steps are. Once we have an update to share, we'll post it here.
brtrach 246 Reputation points

2020-11-30T22:33:26.12+00:00

Just wanted to provide a quick update that the product group is investigating these errors right now. We will share more update as we receive them.
Tim Gregor 1 Reputation point

2020-12-01T00:13:16.577+00:00

Same issue here. Was able to verify APNS using Pusher so it appears certs and app are working properly.
Johny B 21 Reputation points

2020-12-01T17:04:32.14+00:00

This is making me question our decision to go with Azure Notification Hub. The SLA for paid subscription is 99.9% yet it has not worked for 4 days now. If this is a system wide issue, why isn't there any outage details anywhere?
Jon Nichols 1 Reputation point

2020-12-01T17:55:40.26+00:00

We are also experiencing this issue with a brand new notification HUB
Jon Nichols 1 Reputation point

2020-12-01T18:06:08.61+00:00

I've also created a brand new notification Hub, added my server key for Google, Hit test send, got this same error. I am however able to send push notifications in Firebase.
Johny B 21 Reputation points

2020-12-01T18:40:12.727+00:00

I even created a brand new subscription under a new account - still no go. This seems to be a system wide issue yet there's not much noise around it.... makes me wonder how well is this product supported... we're in the middle of migrating from appcenter.
Ehrlish, Robert 1 Reputation point

2020-12-01T22:46:54.607+00:00

Same problem. Been messing with this for days and just found this post..

Hopefully the problem can be resoled soon

Answer 1

brtrach-MSFT 7,386 Microsoft Employee

Hello All, the product group believes they located the issue and took action to resolve it. We are receiving successful reports from customers.

We apologize for the impact that this caused and thank you for your patience as the product group worked towards resolving this matter.

Johny B 21 Reputation points

2020-12-02T19:09:51.75+00:00

Thank you for taking care of it! Its back to normal!
dsav 16 Reputation points

2021-05-10T15:58:03.247+00:00

Seems that this issue is happening again.

Our notification hubs are timing out across multiple subscriptions
AdminLimolane 1 Reputation point

2021-11-30T12:23:10.117+00:00

Hello.
I'm having issues trying to send a test notification with this message:
{"error":{"code":"GatewayTimeout","message":"The gateway did not receive a response from 'Microsoft.NotificationHubs' within the specified time period."}}
I'm sendind directly from portal dashboard and no clue on how to solve this.

Answer 2

Baha Masoud 41

I received this message from Microsoft, and it's working for me now.

> The product team let us know that the issue should be mitigated. Could you try it out and let me know if it is successful?

Jorge Garcell 11 Reputation points

2020-12-02T16:34:47.017+00:00

I don't get the error anymore and it says that the notification was successfully sent but it doesn't get throught firebase. I tried romoving the Firebase Server Key and creating a new one and I used it in a new Azure Hub but it didn't work, I get a success message but the notification doesn't reach the client App. If I send it directly from Firebase it works as expected.
Baha Masoud 41 Reputation points

2020-12-02T16:44:27.58+00:00

i had the same issue,
so I forced the device to registered again (removed the storage), and tried to send the message and was successful.

Answer 3

Jon Nichols 1

Something must've changed this is working for me now as well.

Answer 4

Ramakrishna Sriramoju 1

Hi Team,
All existing notification hubs are not sending notifications. Everything got failed with Timeout exception.

Ramakrishna Sriramoju 1 Reputation point

2021-05-11T13:51:19.24+00:00

Now all notifications are going out.

Answer 5

dsav 6

Wondering if this is an issue again?

Noticing today (and over the weekend) that some push notifications are timing out while others are taking 30+ seconds to complete.

Send a test push notification. Error Code: GatewayTimeout

4 additional answers

Activity