You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Azure Notification Hub SDK 1.0.9:NotificationOutcome属性含义咨询

Understanding Success and Failure in NotificationOutcome (Azure Notification Hub SDK 1.0.9)

I totally get it—official docs can be frustratingly vague on these granular details. Let me break down exactly what those two values mean when using SendDirectNotificationAsync:

When you send a direct notification to specific devices (targeted via their PNS handles), the NotificationOutcome properties map directly to the immediate results of that send operation:

  • Success: This integer counts the number of devices where the push notification service (like APNS, FCM, WNS) accepted the notification and confirmed it’s queued for delivery. It doesn’t mean the device actually displayed the notification (e.g., if the device is offline, the PNS will hold it for later delivery—this still counts as a success). It only reflects that the PNS acknowledged the request as valid and processable.

  • Failure: This counts the number of failed delivery attempts. Common reasons for failures include:

    • Invalid or expired PNS handles (the device unregistered, or the token rotated without your app updating it)
    • The PNS rejected the notification payload (e.g., malformed JSON for FCM)
    • Temporary PNS service errors (though some transient failures might be retried automatically by the hub)
    • Exceeding PNS-side quota limits

Keep in mind these are real-time acknowledgment counts from the PNS, not end-to-end delivery confirmation to the user’s device.


内容的提问来源于stack exchange,提问作者Imixal

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.21 06:48:59