@sujith given the fact that we are paying for historical API subscription and sticking to the prescribed TPS, it cannot result in timeouts all the time. This has been the case even in off-market hours.
Please look into it on priority and get this …
Hi @sujith
This is not the case. I am again trying now, I am getting the same error. This does not happen for websocket, but only for Historical. I have not tried any of the other apis so far.
Also, this behaviour is not consistent. The same pyt…
Hi @sujith , I am again trying today, this is again happening. i mean when can i be sure that you're not running maintenance?? i have seen a lot of threads with the same reason being given. can you please check again if things are fine at your end??
@sujith Even I am facing the same issue with the historical API. Token exception: Invalid API credentials. It is currently very arbitrary. Happening even on a weekend multiple times.
@v4vikash Do let me know if you figure out the issue here