Issue when trailing stop loss

[yades]

Hi Support,
I just realized that my trailing stop script that works fine in back testing is not working as I expect it too in live trading. What I expect the script to do is simply check different conditions and trail the current stop loss in order to lock in further profits on each primary bar update. The problem I am experiencing is that the current stop loss is cancelled on bar update but the new stop loss is calculated (as I see it in the Print field) but is not entered, therefore I end up with a position but with no stop loss. Are you able to spot anything erroneous in my script? I was thinking it could be the part highlighted in bold, but if I eliminate that I end up having 2 stops in the market, the old one and the new one..

if(BarsInProgress == 0)	// primary time frame (e.i. 60 min)
{
	#region Long - Stop Loss Management
		{
		if(Position.MarketPosition == MarketPosition.Long && stopOrderLong != null)
			{      
                           if(conditionA == true)
                                 {
                                      stopPriceA = Low[0];
                                 }
                           if(conditionB == true)
                                {
                                       stopPriceB = Low[1];
                               }
                          }
double newStop = Math.Max(stopPriceA,stopPriceB); 	// calculate new stop loss
if(newStop > stopOrderLong.StopPrice) // check if new stop loss is higher than current stop loss
{
	if(newStop < Close[0])
{
	[B]CancelOrder(stopOrderLong);[/B]
	stopOrderLong = ExitLongStop(1,true,stopOrderLong.Quantity, newStop,"","");
}
else if(newStop >= Close[0])
{
	CancelOrder(stopOrderLong);
	ExitLong(1,stopOrderLong.Quantity,"","");
}
}

[NinjaTrader_Bertrand]

yades, the cancellation seen must come from your explicit CancelOrder call since liveUntilCancelled is set to true, meaning the orders would not expire and persist until you cancel them or the session end handling for DAY orders would take over. The stop should only need to be cancelled once the position is closed (for example by your target or market exit) - if you just want to update the stop then a call to the same stop order / signal name would provide the update you seek, also eliminating the issue of having two stop orders in the market to deal with, as you would always update the old one until either stopped out or closed by other means.

[yades]

Berthand, yes I just want to update my stop or alternatively exit at market.So if I understand correctly what you are saying is:
1) I need to remove CancelOrder(stopOrderLong); from the script below;
(2) I must be sure that the both my initial stop and my new stop loss have the same signal name ( currently that is not the case, as I am calling my initial stop "stoploss" and my new stop "newstop").

Please advise if I understood correctly what you are saying to me.

Moreover, in case I exit at market (as described in the last part of my script, will NT automatically cancel my stop loss?

yades, the cancellation seen must come from your explicit CancelOrder call since liveUntilCancelled is set to true, meaning the orders would not expire and persist until you cancel them or the session end handling for DAY orders would take over. The stop should only need to be cancelled once the position is closed (for example by your target or market exit) - if you just want to update the stop then a call to the same stop order / signal name would provide the update you seek, also eliminating the issue of having two stop orders in the market to deal with, as you would always update the old one until either stopped out or closed by other means.

[NinjaTrader_Bertrand]

You are correct in understanding, just resubmit the order with the same signal name and your new price, this will just be updating the currently residing one. Correct if the managed position is closed, the stop would be cancelled in NT's managed mode.

[yades]

Bertrand, could you please further elaborate on this point, I am not sure I understand what you mean here.

yades, the cancellation seen must come from your explicit CancelOrder call since liveUntilCancelled is set to true, meaning the orders would not expire and persist until you cancel them or the session end handling for DAY orders would take over. T

[NinjaTrader_Bertrand]

Per default in NT's managed approach any order will expire on the next OnBarUpdate(), meaning you would need to resubmit, or use the more advanced overload that would let you explicitly set the liveUntilCancelled parameter to 'true' to override this handling. Then the order will not be cancelled unless you CancelOrder() it, or the end of session handling would if orders were placed with a TimeInForce of DAY.

[yades]

ok this is all v clear, thx

Per default in NT's managed approach any order will expire on the next OnBarUpdate(), meaning you would need to resubmit, or use the more advanced overload that would let you explicitly set the liveUntilCancelled parameter to 'true' to override this handling. Then the order will not be cancelled unless you CancelOrder() it, or the end of session handling would if orders were placed with a TimeInForce of DAY.