Matt Stancliff
Matt Stancliff
> i only got the issue when i fetch executions oh, I see what you're saying. If it works with NONE, then it must mean somehow your IBKR historical data...
If IBKR decides to not reply to a request, the APIs can just hang indefinitely like that sometimes (it's why the regular calls have timeouts attached in different places because...
> I did secType="OPT" on the ExecutionFilter and it avoided the COMBO as i wished.. Interesting! If only automatic execution fetching causes problems, you can just disable it with the...
> i kinda need executions to better track commission/fees Oh — this may help: the startup loading only fetches the recent _history_, but you always get live updates of new...
good to know. This should be adjusted to have the new working default but also allow overrides with an env var if provided: https://github.com/ib-api-reloaded/ib_async/blob/2afdae44a47f067bf3d1a23a4840234f2906ef64/ib_async/flexreport.py#L71
Some things to check: - IBKR doesn't provide unlimited data and will slow you down if you request too much (and they don't always say what "too much" is): https://interactivebrokers.github.io/tws-api/historical_limitations.html...
> I have just discovered that If i adda **timeout** to my request, it comes back much much faster Now that you mention it, I remember the same thing now....
Yes, you are correct! I don't see why it was done that way originally and I fixed it for the next release here, so the behavior of that tracked value...
> Since IB updates price (tick type 4) and size (tick type 5) independently, I don't remember the exact logic trace, but I believe IBKR does combine some data updates....
What could be happening: - `trailing_stop_order` is submitted without an account id - but `place_order()` updates `trailing_stop_order` to populate the account id - now `stop_loss_order` is submitted _without_ an account...