ExitLongStopMarket is filled and Strategy enter again

[milfocs]

The strategy works perfecly in playback but in real when the Exitlongstopmarket or the ExitLonglimit is filled, I understand that it places the Exitlong again. Not always, 30% of times.
If Exitlong is filled, we aren't in MarketPosition.Long, then why it places the order again? I thought maybe it was because the latency o something, but I bought a good vps and it's still the same. thanks

if ((Position.MarketPosition == MarketPosition.Long)
&& (Value == 3)
&& (Close[0] < Primertrigger))
{
ExitLongStopMarket(Convert.ToInt32(DefaultQuantity ), Stoploss, "", "");
ExitLongLimit(Convert.ToInt32(DefaultQuantity), Profitvalue, "", "");

}

[NinjaTrader_Gaby]

Hello milfocs,

Thank you for your post.

To understand why the script is behaving as it is, such as placing orders or not placing orders (or drawing objects or other actions) when expected, it is necessary to add prints to the script that print the values used for the logic of the script to understand how the script is evaluating.

In the strategy add prints (outside of any conditions) that print the values of every variable used in every condition that places an order along with the time of that bar.

This will print to the output window. Backtest the script and when the output from the output window appears save this by right-clicking the output window and selecting Save As... -> give the output file a name and save -> then attach the output text file to your reply.

Output from prints will appear in the NinjaScript Output window.
NT8: New -> NinjaScript Output

The prints should include the time of the bar and should print all values from all variables and all hard coded values in all conditions that must evaluate as true for this action to be triggered. It is very helpful to include labels and operators in the print to understand what is being compared in the condition sets.

Below I am providing a link to videos that demonstrate adding prints to a script to get further information about the behavior of the script.
NT8 —

https://youtu.be/H7aDpWoWUQs?t=2577&list=PL3-s3qsUnfLSC7zCAc5ZmVnauWXkWe0Nf&index=14

It is also helpful to set TraceOrders to true in State.Configure as well as print the order object in OnOrderUpdate().
TraceOrders will output to the NinjaScript Output window a message when orders are being submitted, ignored, cancelled, or rejected.
Printing the order object in OnOrderUpdate() will allow you to track the progression of the order from submitted, to working, to filled, cancelled, or rejected.
These tools will let you know what happens to the order.
TraceOrders - https://ninjatrader.com/support/help...raceorders.htm
OnOrderUpdate() - https://ninjatrader.com/support/help...rderupdate.htm

I'm also including a link to a forum post with further suggestions on debugging a script.

https://support.ninjatrader.com/s/article/Developer-Guide-Debugging-using-Print-and-TraceOrders

Save the output from the output window to a text file. Let me know if you need assistance creating a print or enabling TraceOrders.

I am happy to assist with analyzing the output from prints and TraceOrders.