Segmented push notifications fail to send RRS feed

  • Question

  • We send push notifications to our users via the built-in functionality in the Developer Dashboard. 

    Unsegmented push notifications are always sent and delivered correctly.

    Segmented push notifications - that is, notifications that target a specific Customer Group - always fail (0% delivery rate, or occasionally, perpetually in the 'scheduled' container even after the scheduled date is in the past). 

    We've verified this behavior across several accounts, including accounts operated by other developers. 

    • Moved by Breeze Liu Monday, March 5, 2018 3:09 AM engagement framework issue
    Friday, February 9, 2018 6:46 PM

All replies

  • I too have never managed to get a targeted notification wo work. It goes to no-one.

    Saturday, February 10, 2018 12:42 AM
  • Hi ductionist,

    Sorry for the delay.

    Could you please offer more information about this issue? What kind of devices and what's the OS version for the devices?

    Best regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, February 14, 2018 8:22 AM
  • Thanks for responding.

    The target devices are primarily Windows 10 desktops, with a small number of Windows 10 Mobile users. 

    OS version for the devices varies but ~80% of them are on Creators Update or newer. 

    Wednesday, February 14, 2018 10:46 PM
  • <style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; color: #454545} </style>

    Hi, just wanted to provide an update on this. We scheduled another test push to a customer group, and this time it was sent to a non-zero number of users.

    We didn't change anything (the push contents and customer group were identical), but it looks like the problem has been resolved. Thanks!

    • Proposed as answer by Barry Wang Tuesday, February 20, 2018 8:38 AM
    Friday, February 16, 2018 11:26 PM