Quote from mon:
I am going to be watching my IB executions very closely
IB stated about 4-5 months ago they have removed 3 requirements for stop to be executed which causes slippage
my stop didn't execute today when LAST TRADED price touched it in YM
Lets hope this is just one freak occurrence and that IB didn't bring back the silliest rules for definition of "LAST" that I have ever seen in this industry
Quote from OldTrader:
How do you have your stops configured? Are you aware there are 6 different trigger methods for stops?
Did the future trade thru your stop, or just touch your stop?
Obviously if it traded thru that's a problem. If it just touched it might be a configuration problem. Clearly though, if it just touched and you were not executed, that's a good thing isn't it?
OldTrader
Quote from R. Raskolnikov:
Yeah, I'd MUCH prefer to have a stop hit and watch price continue in my original direction than to have my software fail and me get lucky.
Quote from def:
There is no proof that the software failed here. Mon, I'd suggest you send the info to CS via a ticket and ask them to look into what happened. There is no need to guess here as it should all be part of the audit trail. In the meantime, i you haven't please check your config to make sure your stops are indeed set to default and/or last.
Quote from def:
There is no proof that the software failed here. Mon, I'd suggest you send the info to CS via a ticket and ask them to look into what happened. There is no need to guess here as it should all be part of the audit trail. In the meantime, i you haven't please check your config to make sure your stops are indeed set to default and/or last.