Interactive Brokers TWS Bug Thread
- Thread starter Kensho
- Start date
The problem during resets is with execution of open orders and not with orders disappearing from the server (that has never happened to me).
Sometimes stop or target order will get executed properly, and sometimes the price will slice through your order level and nothing happens or a stop-market order gets executed later at a different price.
But as long as stop/target level is never hit during the reset, there won't be any problems, all open orders will be present after the reset ends and will be properly executed later. So there is really no need to cancel and re-enter orders.
You will need to figure out how to deal with all this on your own (when trading longer time frames). If your stop on EURUSD is 100 pips away from the current price at 23:45 ET, then there is probably nothing to worry about, but if it is 10 pips away then it might be a good idea to close the position and re-enter after the reset.
I had the exact same thing happen in all futures markets last week on 5/31, I would place an order (non-API) and get the cyan status for 5 secs before it turned green, yet if I watched the DOM my order was obviously going to the market instantly. Fill reports had the same delay, i.e. I would see a market trade through my limit order, so obviously I'm done but TWS wouldn't give me the report for 5-10 secs later.
Sometime that evening my TWS went pink on its own (a few hours before the midnight reset), reconnected, and the problem was gone. I did several manual resets before that which accomplished nothing.
Support was useless because my audit trail was timestamping everything retroactively to the time of the exchange acknowledgment, not when TWS actually reported acks/fills to me.
So far so good, I haven't seen the problem since 5/31.
I have continuing problems with this and they won't fix it.
They tell me I entered the order after I say it should trigger. This despite sending them a screen shot showing a time with the order clearly visible. Should have triggered but didn't. They say that according to their audit trail I didn't enter it till after my screen shot. Unbelievable!!
They tell me I entered the order after I say it should trigger. This despite sending them a screen shot showing a time with the order clearly visible. Should have triggered but didn't. They say that according to their audit trail I didn't enter it till after my screen shot. Unbelievable!!
I was on 926.5 standalone and updated to 926.6 in hope that it would fix an old bug that was similar to the bug mentioned by Bob 111 on 06-08-12 ("if you move your mouse..."). That old bug happens only sporadically so I don't know yet if it's been fixed in 926.6.
However, starting with 926.6 I've noticed that if a window (IE, eSignal chart etc.) is activated and then you click on the price ladder in BT there is something that flashes on top of BT. It disappears too quickly to tell what it is. Not a big problem, but would seem to be directly related to the fix in 926.6. Have seen it on 2 XP computers.
I was too busy yesterday to fully check out the above.
I have 2 BookTraders open with one on top of the other as in the attached. When you activate an application other than TWS and then click on BT, the portion of the underlying BT that is covered pops up over the top one. I've used this set up for years, so I know that it started with 926.6. Actually the same thing will happen with any TWS window that is partially covered by another.
IB -
Many thanks for resolving the Java scroll issues (without having to double-click), 926.5 is working great.
One order management bug someone else mentioned which still appears in 926.x is if you have *multiple* working orders on the new exchange routed intercommodity spreads (RB.CL or HO.CL) and you disconnect/reconnect TWS, only one of those orders will reappear in pending upon reconnecting.
When this happens, the only way to cancel orders is to go into webtrader or a pre-925 TWS.
Not sure if this has been fixed in 927/928. If it makes any difference, I do have the old non-guaranteed generic SMART "synthetic" combos quoted side by side with the exchange ones, not sure if my TWS is somehow getting confused.
Also noticed upon reconnecting sometimes the orders that do show up in pending have an inverted description, i.e. the original quote line was AUG12 +RB -CL and upon reconnect it shows up as AUG -CL +RB. I don't care about this, I just bring it up in case it's related to the problem.
Many thanks for resolving the Java scroll issues (without having to double-click), 926.5 is working great.
One order management bug someone else mentioned which still appears in 926.x is if you have *multiple* working orders on the new exchange routed intercommodity spreads (RB.CL or HO.CL) and you disconnect/reconnect TWS, only one of those orders will reappear in pending upon reconnecting.
When this happens, the only way to cancel orders is to go into webtrader or a pre-925 TWS.
Not sure if this has been fixed in 927/928. If it makes any difference, I do have the old non-guaranteed generic SMART "synthetic" combos quoted side by side with the exchange ones, not sure if my TWS is somehow getting confused.
Also noticed upon reconnecting sometimes the orders that do show up in pending have an inverted description, i.e. the original quote line was AUG12 +RB -CL and upon reconnect it shows up as AUG -CL +RB. I don't care about this, I just bring it up in case it's related to the problem.
Happens in 927.7 too.