Right of the bat, the 3 connections rate limit hit us pretty hard, causing most of our systems to become dis-functional over the last week or so.
Nevertheless, we went ahead and decided to create and pay for new kite apps since the streaming market data is indispensable to us.
So, we now have two apps (using the same client ID).
However, even with the new app and a brand new Access Token, we are not able to open a new websocket connection. The very first attempt to test it through a new connection via the chrome dev console resulted in the same dreadful 429 response.
Browsing through the forums, it is evident that quite a few people are facing similar issue.
Could you please clarify if there is something we could be doing wrong, or is it an issue that has cropped up because of some buggy logic you guys pushed while enforcing the 3-connections rate limit recently. If latter, when can we expect a resolution.