Is the order engine broken on historical orders? Orders stuck in working state.

[NinjaTrader_ChelseaB]

Hello koganam,

I was asking for you to export and repost as the link on your first post is not working.

[koganam]

Hello koganam,

I was asking for you to export and repost as the link on your first post is not working.

Here is the zip file.

It looks like there is more to it than a historical overfill. When I use the settings in the picture attached, I get the VERY FIRST entry order stuck in working order, with the protective orders never even placed. The very first order, dated 10/17/2014.

[NinjaTrader_ChelseaB]

Hello koganam,

I see there is a lot of extra log in this script, so the first thing I have done is remove all of the extra logic and left just the code for the entries, that you feel is causing the issue.

Looking at this I am seeing code that is warned not to do in the help guide.

_oLongEntry = EnterLong(TradeQty, "Long");

"OnOrderUpdate() will run inside of order methods such as EnterLong() or SubmitOrderUnmanaged(), therefore attempting to assign an order object outside of OnOrderUpdate() may not return as soon as expected. If your strategy is dependent on tracking the order object from the very first update, you should try to match your order objects by the order.Name (signal name) from during the OnOrderUpdate() as the order is first updated."
https://ninjatrader.com/support/help...rderupdate.htm

Assigning the order to a variable (or array element) must be done from OnOrderUpdate(). See this 'ProfitChaseStopTrailExitOrdersExample_NT8' example.
https://ninjatrader.com/support/foru...269#post802269

Further, you have a print that appears when _oShortEntry is null, but this is in no way attached to the EnterLong() below it which will be triggered every time that line is hit from the condition above. This is because only the next command is triggered by the branching command without curly braces.

if (/* condition */)
Print("condition true"); <--- only printed if the condition is true
EnterLong(); <-- always submitted as it is not within the 1 command action of the condition above

if (/* condition */)
{
Print("condition true"); <-- only printed if the condition is true
EnterLong(); <-- only submitted if the condition is true
}

If you are intentionally submitting these when the outer condition is true, non-reliant on the condition above, let me know.

I had to change this before even running the test, which breaks the rest of the logic of the script, as this goes against the notes in the help guide. These notes are because of the unexpected behavior that can occur.

However, with just the entries uncommented, I'm not seeing the first order is getting stuck.

Below is a link to a video of testing.
https://drive.google.com/file/d/1NJm...w?usp=drivesdk

Placing the entries does not seem to be the issue. Before moving forward, please correct the script so that no orders are being assigned to variables outside of OnOrderUpdate().

Then, ensure that the behavior is not caused by placing the entries as I have done first, to see if it is the additional logic causing the issue.

Uncomment code, one line at a time to track down where the issue begins. Likely, you will find where additional orders are being submitted.