Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to move to higher tier WNS based on doc recommendation when receiving 429? #5238

Open
LexMaxis opened this issue Dec 11, 2024 · 0 comments
Labels

Comments

@LexMaxis
Copy link

Type of issue

Missing information

Feedback

Issue Definition

In January 2024, the My customer App PC client integrated WNS push notifications through the Microsoft documentation.

The cloud service utilizes Windows system notifications by calling the following API interface to deliver:

  • Operational recommendation messages
  • IM communication notifications

This ensures continuous user engagement and stable growth in active users.

Until 16:24 (UTC+8) on December 4, 2024, the QPS (queries per second) of the above API calls remained below 1k without any issues.

However, at 16:24 (UTC+8) on December 4, 2024, the QPS exceeded 1k, causing the interface to return a 429-rate limit error code.

Error Details

{
  "MsgID": "",
  "DebugTrace": "",
  "DeviceStatus": "",
  "ErrCode": 429,
  "ErrDesc": "App is throttled. Wait for the seconds of the value in Retry-After header and try again"
}

Where we stop

Based on troubleshooting guidance, we received a suggestion but do not know where to click the button or apply for moving to a higher tier WNS.

Reference


Customer Analysis and Concerns

The customer analyzed the issue and raised the following questions:

  1. Scaling Up WNS Service: Is it possible to scale up the WNS service as per the documentation? If so, what information needs to be provided by the customer for backend operations?
  2. Increasing Rate Limits: Can the current QPS rate limit (1k) be increased to 5k or 10k?
  3. Bulk Push Interface: Is there a bulk push interface available that aggregates multiple device tokens for delivering the same message to improve throughput?
  4. Direct Contact with WNS Team: Can the customer directly contact the WNS team via [email protected] or another address for further assistance?

If any additional information is required, please let us know. We are happy to provide further details or arrange a quick discussion via separate Email thread t to expedite the resolution process.

Work email Contact: [email protected]

Page URL

https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/push-notifications/troubleshooting

Content source URL

https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/push-notifications/troubleshooting#:~:text=429%20Monthly%20Quota,higher%20WNS%20tier.

Author

drew batchelor

Document Id

https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/windows-app-sdk/notifications/push-notifications/troubleshooting.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant