Joachim Karlsson
Joachim Karlsson
+1 for this!
Thanks that is what I mean. It seems to me that this is a very big problem. So I will.
It's a good question. First it should probably not allow any more requests to be done within the same session to that endpoint. Then I got a strange error. Tried...
One small improvement could be also for the 429 not just send ExternalBrokerError since you then have to investigate the error to see if it's a 429.
Adding to that. If you don't have market data access. It should not do any retries. This was using: marketdata_history_by_conid
What do you mean that 'it seems to loop a lot more'? There's a reattempt logic when encountering ReadTimeout error, but other than that not sure what kind of loop...
I am getting a distinct feeling that it's an intentional block from IB. This seems to happen during night time. If we get into problems during night time and continue...
When I look at this again. It seems like the main issue here is if the client get disconnected IBKR seems to send a not recongnized page by the login...
I seems like this is because of the websocket library being to new. websockets==10.4 seem to work. However even if I am connected there is no Quotes coming for OMXS30....
It seems like there is sometimes a certificate problem. I don't know why it worked intermittently. But to make it always connect to the socket I added. ``` import ssl...