Azure NotificationHub - bad notification detection

I am trying to save failed notifications in dbe.g. the client does not have internet access. This will allow me to check with backgroundServiceif there is no notification, and then create it from backgroundService.

Therefore, on my Azure App Service Mobile:

I have the following:
var notStat = await hub.SendWindowsNativeNotificationAsync(wnsToast, tag);
telemetry.TrackTrace("failure : " + notStat.Failure + " | Results : " + notStat.Results + " | State : " + notStat.State + " | Success : " + notStat.Success + " | trackingID : " + notStat.TrackingId + ");

The code snippet was supposed to check the influence of the client, but no matter what I do, the summary log is just a message enqueued.

Question

So how do I detect failed notifications?

Conclusion

To summarize the discussions with the accepted answer:

When a notification is sent, NotificationIdand other relevant data is stored in a separate table.

, , . .

, , background task. , background task, . 6 background task . background task , .

+2
1

- . . , , EnableTestSend -

".State Enqueued - , . EnableTestSend boolean" (c) documentation

, EnableTestSend , ( , , ).

Permet Telemetry REST API, - Fiddler + .

, , SO, , : .

, , ( ) FAQ - , , , -, (, , , , , ..).

+2

All Articles