You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using macOS, TWS 10.30.1i (current Latest) and TWS 10.31.0i (current Beta), ib_async is unable to fetch executions. Depending on the setting of the new Global Configuration > API > Settings > Download Execution Report, one of the following happens (at least when the account being queried does have executions for the current day)
If "All Available": reqExecutions returns but none of the day's executions are returned. No execution data appears in the TWS logs.
If "Today": reqExecutions hangs and TWS never sends the "end executions" message (tick 11). No execution data appears in the TWS logs either. On connection, ib_async will print "executions timed out" indicating reqExecutionsAsync has timed out.
This issue also occurs when using the native IB API on both stable and latest branches, so it's unlikely to be related to ib_async, however I'm posting this here in case others run into this issue.
The text was updated successfully, but these errors were encountered:
Anyone still experiencing this issue? After using ib_insync for years, I'm suddenly having problem pulling fills and executions in my paper trading accounts. I've updated to more recent versions (currently on 0.9.82 of ib_insync) but thinking I probably should make make the switch to the new libs.
Actually look like the fills in my paper trading account are now showing up again when I change the setting mentioned above: Global Configuration > API > Settings > Download Execution Report. Changed this to "Today" and I'm now seeing some fills. Huge relief!
Using macOS, TWS 10.30.1i (current Latest) and TWS 10.31.0i (current Beta), ib_async is unable to fetch executions. Depending on the setting of the new Global Configuration > API > Settings > Download Execution Report, one of the following happens (at least when the account being queried does have executions for the current day)
reqExecutions
returns but none of the day's executions are returned. No execution data appears in the TWS logs.reqExecutions
hangs and TWS never sends the "end executions" message (tick 11). No execution data appears in the TWS logs either. On connection, ib_async will print "executions timed out" indicatingreqExecutionsAsync
has timed out.This issue also occurs when using the native IB API on both stable and latest branches, so it's unlikely to be related to ib_async, however I'm posting this here in case others run into this issue.
The text was updated successfully, but these errors were encountered: