Ultimate handling for rejected stops...how?

[SIFTrader]

I am trying to ensure that I robustly handle any rejected stop orders when they are placed on the wrong side of the market due to fast moving markets.

For real-time, I overrode the default error handler, and then submit it as a market order.

However, this code does not fire in backtesting...so I implemented a basic check of:
if (price == stop price) then market order entry, else stop order entry.

That seems to work, but my question really is how to best code so that the same code will be used for both real time and backtesting?

Is that possible, or is my solution above the recommended method?


And, will NT7 simply have a built in option to handle rejected stops so that they can be resubmitted as market orders or should I just add the default override of the error handler for all my systems?

I am porting from TS because I am tired of their inability to handle rejected stops btw...so this is quite a key issue for me.

Thanks

[NinjaTrader_JoshP]

SIFTrader,

Since backtesting is different than real-time, the approach you used will be the one to take.

If you wish to control it to become a market order I would recommend programming the logic yourself.

[aviat72]

SIFTrader/Josh:

Can you point me to any link on how to override the default error handler?

I need to take care of exactly the same situation.

This is one of the most pernicious problems when trading some instruments because often the exchange (e.g. GLOBEX) will cancel your order instead of executing it as you intended!

Thanks

[NinjaTrader_Ben]

Hello,

I will have someone reply to you on Monday. Thank you for your patience.

[aviat72]

Hello,

I will have someone reply to you on Monday. Thank you for your patience.

Bump...
This is an important topic in any robust system so any pointers will be useful

[NinjaTrader_Bertrand]

aviat72, sorry for our delay - you can turn off auto error handling by setting RealTimeErrorHandling to TakeNoAction - http://www.ninjatrader-support.com/H...rHandling.html

Of course it's your responsibility then to properly account for all scenarios involved.