@sujith Thanks for the info. If these are the latest Docs - https://kite.trade/docs/connect/v3/websocket/ - They say that 1000 instruments can be subscribed per websocket. They probably need to be updated. Unless of course I was viewing an outdated …
Thanks @sujith, will see how it goes. But the Bad Gateway errors still persist. For example, this morning, the API just shot back a 502 Bad Gateway for 30 minutes. Now that's a long time. A few minutes is understandable. But 30 minutes is kind of pu…
I have seen this error only for the historical_data API.
The only way I'm still able to tolerate this is by catching the exception when it throws a 502 Bad Gateway and just indiscriminately requesting the data again in a loop till it grants the req…
@sujith This issue needs to be resolved. Is this an issue from your end? What can I do to fix it or handle it from my end? Any response would be appreciated.
Upgrading the version fixed everything. Thank you so much. Looks like I overlooked something very basic. Sorry for wasting your time and I appreciate the support
I'm using version kiteconnect version 3.6.2
I'm instantiating a Websocket after importing it from the kiteconnect library for my userID. It connects fine and a websocket is generated.
I've defined an on_message method which I've assigned to the on_m…
