Interactive Brokers stop order not executed !

Question for the original poster...

Did you have a plain old vanilla bracket order and the price ran right through your stop and zero execution by IB?

Did this have something to do with your api?

I run brackets all the time, never had one problem.

Lately I split my orders in two where entrance and exit and stops are slightly different as this is my method of scaling, I’m assuming this will limit my risk IF for some reason 1 stop on one of my brackets misfires my other bracket should hold true... I hope.
 
d08 said:
You can't just lump all recent IB issues together and claim they stem from the same original problem, not without any proof anyway.
More...

When disparate, formerly-stable trade set-ups, having run thousands of trades in different markets and from different locales, simultaneously develop execution issues which impinge (or outright deny) operability, then a little Boolean logic ....... yeah. Nah. Nevermind.... :rolleyes:o_O:confused::(
 
Last edited:
tommcginnis said:
When disparate, formerly-stable trade set-ups, having run thousands of trades in different markets and from different locales, simultaneously develop execution issues which impinge (or outright deny) operability, then a little Boolean logic ....... yeah. Nah. Nevermind.... :rolleyes:o_O:confused::(
More...

The OP did not specify the problem at all. He didn't ask IB about it nor told us what color the status was (from which we can determine the order state). For all we know the order was already at the exchange and it was an exchange issue.

I have had order state issues with IB before and it was reported nowhere else, after a few days it was quietly fixed and it appeared to stem from a response on one specific exchange. I didn't assume every other IB order problem at that time was connected to that.

reqPositions is an internal IB query that has no connection to anything on the exchanges.
I hope you don't diagnose other technical problems with such guesswork and rely on solid evidence and facts instead.

Anyhow, I don't see what the OPs goal here was. Just to stir the pot? He clearly didn't want to find out the real problem or solve it.
 
Yeah I had some strange behaviour recently, one error was the result of human error because one of the preset conditions was ridiculous , for example I was trading sugar and the price of the contract was 0.1090 and when I selected stop order the price automatically populated by the System was 1.1090.

so for example when I'm trading oil that it might change the price in a more reasonable increment because it's using an absolute number to distance itself from the current market price such as 1.00
So the stop suggested by the oil price when the market was it 65 something would be 66 something. Obviously in the case of something with it much smaller outright price in absolute terms, that change becomes ridiculous.

Once they pointed this out I noticed it was a preset condition whenever I added a stop order.

That was an expensive mistake to learn but does anyone know if there's a feature where the preset suggested price is 2% from the current market price?

There are other examples I've had only recently where the price seem to trade through the stop without any explanation and Interactive Brokers didn't want to hear about it.

I couldn't get any Clarity on why they traded through but I need to pay more attention to the colours of the order in case that's my issue because I normally do accept the outside hours criteria
 
You must log in or register to reply here.
Back
Top