locked
Error Details - So our backend can catch and react on errors RRS feed

  • Question

  • Hi there,

    I would need detailed information what kind of errors we could expect when we use the REST API to send notifications. Currently it seems we are always getting a HTTP 200 OK status even if the message was actually not delivered to the device.

    We need to be able to recognize non-delivered messages before our customers actually start complaining. How can we achieve this with Azure Notification Hub?

    Regards, Kristof

    Monday, March 19, 2018 12:42 PM

All replies

  • We apologize for the delay in reaching out to you. If you were able to find a solution, would you mind sharing it with us in case someone else runs into a similar issue?
    Tuesday, May 22, 2018 11:39 PM