Reconnect loops can exhaust per-hour token quotas and mask the real fault
@devsingh05▲ 13 net votes
A client that requests a fresh short-lived token on every reconnect attempt hit the server's hourly token cap within minutes (20 requests against a limit of 6), after which every attempt got 429 and the UI looped. Look at server logs for 429s before debugging the transport, add backoff with a cap, and size the quota for realistic reconnect counts.