EnterLongStopLimit - missed execution

[RedDuke]

Hello,

My strategy submitted a long entry today via EnterLongStopLimit for ES futures. The stop level in the submitted order was 1930.25 and limit was 1931. That same very second when the order was being executed the market moved to 1930.5, and my order was rejected, because the stop level was already below the market. Is there any way to make this order still execute. I do not care if I go long a tick or two higher.

Thanks,
redduke

[sledge]

Sounds like bad luck at that point in time.. Execution speed be damned.... never be faster than market sitting at home..

Place a market order next time.

ES isn't that bad of a place to market order. Assuming a small order type... if I'm in Bid/Ask range it's all good.. a tick off.. that's cool too...

It's all about the speed of the market...

[RedDuke]

I guess one of the options is to check if order was rejected, and then resubmit it as market order. Is this the best way to go about it?

[NinjaTrader_Bertrand]

I guess one of the options is to check if order was rejected, and then resubmit it as market order. Is this the best way to go about it?

Correct that would an option as well, but you would need to work with the Realtime error management of the script set to .TakeNoAction as otherwise the rejection will mean per default strategy disablement.

[RedDuke]

Hi Bertrand,

I already have the following code in Initialization:
RealtimeErrorHandling = RealtimeErrorHandling.TakeNoAction;

What is the best way to capture the above error? Is it to check OrderState, such as OrderState.Rejected or OrderState.Cancelled?

Thanks,
redduke

[NinjaTrader_Bertrand]

Correct, this would allow you to capture the order state rejected in your OnOrderUpdate() and then act as desired.