HTTP 429 indicates that a server is limiting the rate of requests. Repeated retries, rapid catalogue refreshes or several clients can contribute. Stop the retry loop and follow any retry timing supplied by the service.
Reduce automatic repetition
Close duplicate sessions and avoid repeatedly pressing reload. A player may also have scheduled refresh behaviour. Check its supported settings rather than leaving several devices continuously attempting the same failing operation.
Allow the stated interval
Some responses include a Retry-After value, though the player may not display it. Ask support if the limit is unclear. Restarting the app over and over can continue the very request pattern the server is trying to limit.
Report a normal-use failure
If ordinary use repeatedly triggers the limit, provide the app version, operation and approximate frequency. The provider may need to investigate server policy or compatibility. Do not try to evade the limit with additional accounts or changing addresses.
