In this thread, I will expose the workings of this nuclear bomb inside a 2014 version of TWS. I discovered a bug in IB TWS that can potentially destroy your account in one click. I use an older version of TWS like many IB customers who wish to avoid the frequent issues on new TWS releases. So this may not be of concern to you, but nonetheless it's a fact that IB exposed some customers to debilitating losses, most damning is the fact that IB did not acknowledge the problem and apparently did not even investigate it.
I discovered this bug after a series of erroneous trades of the type "fat finger mistake". After a while, I started to question whether it was just me or whether TWS played a role in it. I couldn't possibly make those fat finger mistakes again and again ! Fortunately, I got lucky, every time I managed to exit the erroneous trades with very small losses equivalent to the spread, because the trades were mostly on IDEAL FX at times where volatility had come way down and my size preset were in accordance with account size and very reasonable. As you will understand, your size preset is a key part of this bug or flaw, whatever you call it. Actually I will say the issue is two pronged; there is a "flaw" and there is a bug that prevents you from realizing what the problem is, i.e TWS hid from me the real order that was sent.
Eventually I realized there was something wrong with IB TWS, but I couldn't quite understand what caused the erroneous trades. I couldn't prove anything.
I kept using the same version paying extra attention when placing orders. But of course, it had to happen that one day I would place an order in a hurry and make the "fat finger" mistake AGAIN ! And this time, I really lost money, it wasn't a FX trade it was in a highly volatile and illiquid stock in after hours. Fortunately, the loss was just average but enough to cause my anger . I realized I could have blown my account on that "mistake". I decided to thoroughly investigate the matter, going through all the steps I made when placing the order.
When I found out IB TWS could lead a customer to send erroneous trades with a multiple of its chosen size, all the while hiding the actual working order, IB customer service denied the whole thing and buried the matter in a hurry.
The story will continue tomorrow ...
I discovered this bug after a series of erroneous trades of the type "fat finger mistake". After a while, I started to question whether it was just me or whether TWS played a role in it. I couldn't possibly make those fat finger mistakes again and again ! Fortunately, I got lucky, every time I managed to exit the erroneous trades with very small losses equivalent to the spread, because the trades were mostly on IDEAL FX at times where volatility had come way down and my size preset were in accordance with account size and very reasonable. As you will understand, your size preset is a key part of this bug or flaw, whatever you call it. Actually I will say the issue is two pronged; there is a "flaw" and there is a bug that prevents you from realizing what the problem is, i.e TWS hid from me the real order that was sent.
Eventually I realized there was something wrong with IB TWS, but I couldn't quite understand what caused the erroneous trades. I couldn't prove anything.
I kept using the same version paying extra attention when placing orders. But of course, it had to happen that one day I would place an order in a hurry and make the "fat finger" mistake AGAIN ! And this time, I really lost money, it wasn't a FX trade it was in a highly volatile and illiquid stock in after hours. Fortunately, the loss was just average but enough to cause my anger . I realized I could have blown my account on that "mistake". I decided to thoroughly investigate the matter, going through all the steps I made when placing the order.
When I found out IB TWS could lead a customer to send erroneous trades with a multiple of its chosen size, all the while hiding the actual working order, IB customer service denied the whole thing and buried the matter in a hurry.
The story will continue tomorrow ...
Last edited: