I would like to report a possible bug with NT dealing with IB's Historical Data requests time limitation.
When programming my trading system, I noticed that NT seems to Handle the Historical Data requests Limitation with a timer very well until either :
1. Comes across an instrument that has no history .. or
2. Comes across an instrument that has little history ..or
3. Maybe after a certain number of instruments have been processed.
I didnt spend to much time trying to figure out what was triggering it.
NT seems to then speed up the requests without the timer and activates the IB Historical requests timing limitation.
Because of this, I had to program my system to wait until NT was through with the Historical Update on all tradable instruments and then initiate the requests directly through IB's API for non-tradable instruments(indexes etc..) using a timer also. This was the only work around I could come up with as I am utilizing over 40 different Instruments and Indexes using 3 different time periods.
You may want to have the programmers take a look at this. I am sure that there may be clients that would like to use multiple instruments and indexes in thier strategies like I have, that may not be able to program for this problem.
Thanks for a Great Product,
Joe
Comment