ExitShortStop fired again

[xewoox]

I am running strategy that fire a Sell Short order $829.75 and then put limit stop order at $829.75 after filled the Sell Short order. The actual fill of the sell order is $829.5. What I notice that the BuyToCover limit order never fired even the price go above the limit stop order price.

Short Sell Order happened at 14:45:57
Limit Stop Order happened at 14:46:01

I have attached a screen shot of the chart, the condense Trace n Output log file. I have also prepare the output window screen shots. I notice in the Output window (Output2-2.jpeg), it keep complaining the "there is already a matching, terminal exit order in place". I am not sure what cause it.

I hope this is enough info for you to analyse the problem.

Not enough space for attachment see also the next post

[xewoox]

Additional attachment for this thread

[xewoox]

Sorry for the empty attachment in last post. The additional attachment is in this post.

[NinjaTrader_JoshP]

xewoox,

Your first order was cancelled and once cancelled it is in a terminal state. That is why you get the "matching terminal order" message. What you want to do is just keep your original order alive. You can do this either by resubmitting it on every single bar or just use the liveUntilCancelled parameter.

[xewoox]

I do resubmit if u see my output2-2.jpeg. I send every ticks after cancel
I can send a bigger output file except the forum does not allow

[NinjaTrader_Bertrand]

Hi xewoox, it would be helpful to see the strategy code to further advise. If you don't want to post it here, you can send it to support at ninjatrader com Attn Bertrand. Thanks!

[xewoox]

I have taken the output window and try to make it as concise at the problem I have.
2/17/2009 11:10:13 AM - Issued EnterShortLimit (1, 792.75, "TSSFdMid)
2/17/2009 11:10:14 AM - Filled the order
2/17/2009 11:10:14 AM - Issued ExitShortStop (793.25)
Before 11:10:15:631 AM ExitShortStop Order get accepted (From OnOrderUpdate())
2/17/2009 11:10:15 AM - NT internal about to cancel extiShortStop
Before 11:10:20:631 AM ExitShortStop Order get cancelled (From OnOrderUpdate())
2/17/2009 11:10:46 AM - Issued a new ExitShortStop (793.75)
But the order being ignored, and the reason is 'There already is a matching, terminal exit order in place'
2/17/2009 11:11:04 AM - the ExitShortStop being issued in every ticks from (2/17/2009 11:10:46 AM to 2/17/2009 11:11:04 AM) - but the order get ignored for the same reason
In the output you can see the close price printing at the back of the Order function< e.g. the close price is 794 in the following line appeared in the output window
ExitShortStop (793.75, TSSFdStp, TSSFdMid) - 794

The only way I can get out is to send a ExitShort() order
2/17/2009 11:11:29 AM.

Would you be able to tell me why I can not send out the ExitShortStop after NT cancel the expired order?

[NinjaTrader_Bertrand]

Hi xewoox, thanks for the outputs - the issue is once the order expires subsequent call are ignored for various reason (internal signal tracking). Have you tried this with liveUntillCancelled as suggested by Josh for the original order? Please also check this thread here - http://www.ninjatrader-support2.com/...?t=9043&page=3

[xewoox]

2/17/2009 11:10:15 AM Cancelled expired order: BarsInProgress=0: Order='929a1f6eaa354d0ab2407b85796f858f/Sim101' Name='Buy to cover' State=Accepted Instrument='ES 03-09' Action=BuyToCover Limit price=0 Stop price=793.25 Quantity=1 Strategy='TempoTrader' Type=Stop Tif=Gtc Oco='' Filled=0 Fill price=0 Token='929a1f6eaa354d0ab2407b85796f858f' Gtd='12/1/2099 12:00:00 AM'

May be you can explain to me how ExitShortStop() work. I thought when I fired the exit short stop, it is a market order. I can not do any more changes even I want to. Would you please explain? Thanks.

[NinjaTrader_JoshP]

xewoox,

When you submit an ExitShorStop() it is a stop order. It only becomes a market order when the stop price is hit.

The trace you quoted means the order was not kept alive. You will want to resubmit the order (and any price modifications if you want) on every single OnBarUpdate() to keep it alive. Otherwise it will automatically cancel.