What are business rules for WNS (notification services) to block updates. RRS feed

  • Question

  • Are there protections that are built into WNS to prevent 'bad' things for the Metro tile experience?

    • excessive text
    • too frequent updates
    • images too large for transfer
    • images that don't have the right dimensions
    • integer values too large for badges
    • others?

    I ask this as we are starting to understand by sending messages using the recipes from BUILD conference.  It works for awhile, then it stops.  DNS answers the server request with a 200, but nothing appears after a certain point on the test client.  I'm wondering if there are business rules that freeze out certain tile, badge, or toast behavior that we should know about.     Is the development 'playing' with the system enough to excite some limitations imposed by WNS?

    Friday, October 28, 2011 10:43 PM

All replies

  • Hi Joe,

    I moved this question to a more suitable forum.


    Monday, October 31, 2011 9:28 PM
  • Hi Joe,

    There are.  I do not know if they are published yet however so expect more documentation in all areas as we move towards Beta.  I was able to find this: "WNS guidelines specify that the frequency of these updates should be at most one every 30 minutes. The end user or WNS may determine more frequest routine updates to be abusive." (http://msdn.microsoft.com/en-us/library/windows/apps/hh465460(v=VS.85).aspx)


    Jeff Sanders (MSFT)
    Tuesday, November 1, 2011 12:58 PM
  • Hi Joe,

    Yes there are mechanisms in place to prevent abuse, primarily by limiting the frequency in which notifications can be sent.  This is intended to protect both the end user and service itself.  You will know if you are hitting one of these rate limits because you will get a 406 error from the HTTP response.  If you are continually hitting this error, please let us know.  We're in a constant process of refining our rate limits to ensure the best possible experience for the largest amount of users. For full details of all the response codes and headers please see here:



    On the other hand, if you're not getting an error it could indicate that the payload of your notification could be incorrect.  Often this will happen if your XML schema is not correct or if your images that you reference fails to download.  For more details on the notification templates please see the documentation here:



    • Proposed as answer by Darren Louie Wednesday, November 2, 2011 6:17 PM
    Wednesday, November 2, 2011 4:59 PM