开云体育

thank you for the fast reply. honesty I got lost in i b_insync library ( https://github.com/erdewit/ib_insync ) I'm a?junior so my?knowledge is?quite?limited for now, so I'm not sure how to wait

Yeah, I just checked mine and it's having the same issues. Lou Dudka

My software downloads once per day historical data for about 200 stock tickers. It does so sequentially: one at a time. I have not noticed any change in time it takes for all data to get downloaded:

If you are going to be monitoring the position yourself you just have to change the price on the stop order - you don't have to cancel and submit a new one. Just send another PlaceOrder with

Yes, I am also experiencing the same issue since yesterday.

Does anyone have experience in the mechanics of maintaining a converging trailing stop via the API? I mean a stop where the trailing amount is wide at the start (to give a trade space to take hold)

The most relevant parameter to look at is SMA. If that goes negative you have used too much margin and IB will start to liquidate positions near the end of the US trading day. Some information is

I appreciate you providing a proposed solution, but no...my situation is far from that simple.

Isn't it just adding a function HistPacing() before each request? Inside HistPacing you can use a fixed delay to test things out, then move to keeping a list of the last 60 requests when you're back

I have not been pulling continuously today.? I completely restructured my code years ago when they implemented the throttling on their end.? With their changes today, my new code is totally

skee__bum, I'm OK but I'll try to keep an eye on it.? My logs show occasional data fetches that a taking a bit long, maybe one every 10 mins or so.? I'll try to check back in an hour or so. Did

Lou, I am absolutely still seeing the request pacing violations.? Glad for you if they've disappeared for you, but just be on the lookup, because there still seems to be an issue.

Glad it's working again, Lou. We don't use historical data requests that often (pretty much never) and our code implements self-pacing. So we have not experienced any changes. Just checked our

@skee__Bum Thanks for getting a hold of IB - I just don't have the patience anymore, especially with their short staffing, covid, etc. Whatever tree you shook it seems to be working now (fingers

After getting passed around amongst various IB desks, they said they weren't aware of any changes, but they were seeing the errors on their end.? I provided them with log files and they are going to

@skee-bum YIKES!!!!? Mine started today about 14:35 New York Time. Anyone else? Richard/Jurgen - did you guys hear anything about this? Thanks, as always, and Be Well, Lou Dudka

Years ago, IB expected API users to pace their requests for HMD.? They then moved to a model whereby they paced their responses, and the API users didn't need to pace their calls. But they seem to

The TWS API is asynchronous by design and there is no guarantee as to the time it takes for a response to arrive after the corresponding request has been made. Under no circumstance should you ever

this is my first topic in this gruop so ill start with something simple. on the docs of ibapi it says " *IBApi.EWrapper.nextValidID* callback is commonly used to indicate that the connection is

I'm pretty new to margin trading, and am still trying to wrap my head around how to exactly interpret accountSummary(). Unfortunately, the documentation for it is a bit too terse for