Thanks for the clarification.
So it would be right to assume there is some error on Zerodha's part that's resulting in this issue ?
Could you please raise internal tickets with your tech team regarding the same, if there isn't one already…
As suspected, using a different Client ID did the trick.
So just to be sure of what this implies, is your new rate limit of max 3 connections applicable per `api key` or per `Client ID`?