Announcement

**mw_futures** · 04-12-2025, 08:54 AM

Extra visual information what log looks like.

**NinjaTrader_ChelseaB** · 04-14-2025, 07:06 AM

Hello,

The message 'Cancelled pending exit order, since associated position is closed' means that another order exited the position made by the entry this exit is attached to so it is automatically cancelled.

To confirm, you want the exit order to remain open even though the position was closed by another order?

If so, you would need to use the unmanaged approach.

**mw_futures** · 04-14-2025, 07:15 AM

Originally posted by NinjaTrader_ChelseaB View Post

Hello,

The message 'Cancelled pending exit order, since associated position is closed' means that another order exited the position made by the entry this exit is attached to so it is automatically cancelled.

To confirm, you want the exit order to remain open even though the position was closed by another order?

If so, you would need to use the unmanaged approach.

Hey NinjaTrader_ChelseaB,

Currenty I already use the unmanaged approach.
Example of the intra bar order placement is seen in the 2 images.

The 1st image shows you the entry and that the take profit targets are placed including stoploss.
The 2nd image shows that the first tp target was hit, filled and that the stop contracts have been adjusted.

To confirm, you want the exit order to remain open even though the position was closed by another order?

Currently I already use the unmanaged approach. I always use this and hence why I am confused why the tp targets are closed with this message.
This due to it not being linked to an order of my understanding.

Example code used for the take take partial profits upon complete fill of the limit order:

Code:

PlaceStopLoss();

Print(string.Format("Time {0} : Placing exit MIT orders for LONG position", Time[0]));
if (entryInformationObject.AmountOfContracts125 > 0) placedOrders.Add(ExitLongMIT(0, true, (int)entryInformationObject.AmountOfContracts125, (double)entryInformationObject.Exit125, $"LE125({entryInformationObject.Exit125})({timeID})", ""));
if (entryInformationObject.AmountOfContracts100 > 0) placedOrders.Add(ExitLongMIT(0, true, (int)entryInformationObject.AmountOfContracts100, (double)entryInformationObject.ExitFull, $"LE100({entryInformationObject.ExitFull})({timeID})", ""));
if (entryInformationObject.AmountOfContracts75 > 0) placedOrders.Add(ExitLongMIT(0, true, (int)entryInformationObject.AmountOfContracts75, (double)entryInformationObject.Exit75, $"LE75({entryInformationObject.Exit75})({timeID})", ""));
if (entryInformationObject.AmountOfContracts50 > 0) placedOrders.Add(ExitLongMIT(0, true, (int)entryInformationObject.AmountOfContracts50, (double)entryInformationObject.Midpoint, $"LE50({entryInformationObject.Midpoint})({timeID})", ""));
if (entryInformationObject.AmountOfContracts25 > 0) placedOrders.Add(ExitLongMIT(0, true, (int)entryInformationObject.AmountOfContracts25, (double)entryInformationObject.Exit25, $"LE25({entryInformationObject.Exit25})({timeID})", ""));

where the placestoploss method is just a simple method confirming if we are long, short and how many contracts are on the line

Code:

private void PlaceStopLoss()
{
    foreach (Cbi.Order stoplossOrder in placedOrders.FindAll(x => x == null || x.Name == "Stoploss")) placedOrders.Remove(stoplossOrder);
    if (MarketPosition.Long == Position.MarketPosition)
    {
        if (GetCurrentBid() < entryInformationObject.StoplossPrice)
        {
            Print(string.Format("Time {0}: PRICE ALREADY BELOW 'LONG' STOP EXIT ORDERS", Time[0]));
            ExitAllOrders();
        }
        else
        {
            Print(string.Format("Time {0}: adjust LONG stop contracs to {1}", Time[0], Position.Quantity));
            entryInformationObject.stoplossOrder = ExitLongStopMarket(0, true, Position.Quantity, entryInformationObject.StoplossPrice.Value, "Stoploss", "");
            placedOrders.Add(entryInformationObject.stoplossOrder);
        }
    }
    else if (MarketPosition.Short == Position.MarketPosition)
    {
        if (GetCurrentAsk() > entryInformationObject.StoplossPrice.Value)
        {
            Print(string.Format("Time {0}: PRICE ALREADY BELOW 'SHORT' STOP EXIT ORDERS", Time[0]));
            ExitAllOrders();
        }
        else
        {
            Print(string.Format("Time {0}: adjust SHORT stop contracs to {1}", Time[0], Position.Quantity));
            entryInformationObject.stoplossOrder = ExitShortStopMarket(0, true, Position.Quantity, entryInformationObject.StoplossPrice.Value, "Stoploss", "");
            placedOrders.Add(entryInformationObject.stoplossOrder);
        }

    }
    else
    {
        Print(string.Format("Time {0}: we are flat and doing nothing", Time[0]));
    }
}

As seen in the code, we are using unmanaged MIT orders which are not linked to an entry order. Meaning it should not show the message 'Cancelled pending exit order, since associated position is closed'.

In my other strategies I do not have this issue even though I use the same approach.

Hopefully you could set me into the right direction (maybe some api section I have not yet read) to see to which these exitMIT orders are linked to so I can debug it further and figure out what is happening.

Kind regards, Jelle

**NinjaTrader_ChelseaB** · 04-14-2025, 07:29 AM

Hello mw_futures,

"Currently I already use the unmanaged approach."

The unmanaged approach uses SubmitOrderUnmanaged() for all order submissions.

NinjaTrader Developer Community | NinjaScript Resources & Documentation

https://developer.ninjatrader.com/docs/desktop/submitorderunmanaged

Join the official NinjaScript Developer Community for comprehensive resources, documentation, and community support. Build custom indicators and automated strategies for the NinjaTrader platforms with our extensive guides and APIs.

If you have ExitLongMIT() and ExitShortStopMarket() in the code, this is the managed approach, not the unmanaged approach.

Any Exit method attaches to a specific entry when using the managed approach.

"As seen in the code, we are using unmanaged MIT orders which are not linked to an entry order."

I am not seeing SubmitOrderUnmanaged() in your code.

**mw_futures** · 04-14-2025, 07:32 AM

Hey NinjaTrader_ChelseaB ,

I just did some reading in the API and I see what I have missed.
I will make some code modifications and get back to you!

I indeed made the mistake of not using the correct method.
Thanks for pointing it out! Sometimes through the trees you do not see the forest.

Kind regards, Jelle

**mw_futures** · 04-14-2025, 09:40 AM

NinjaTrader_ChelseaB, extremely good news. Your sharp eyes of mentioning the SubmitOrderUnmanaged() indeed solved it all.
It is working smooooooooth as butter now. Thanks a lot!

Like I said, I think that I did not see the trees through the forest anymore. Such a stupid mistake...

Kind regards, Jelle

Topics	Statistics	Last Post
Clock On Chart Indicator by argusthome Started by argusthome, 03-08-2026, 10:06 AM	0 responses 116 views 0 likes	Last Post by argusthome 03-08-2026, 10:06 AM
RTH Dynamic Session Quarters by NabilKhattabi Started by NabilKhattabi, 03-06-2026, 11:18 AM	0 responses 61 views 0 likes	Last Post by NabilKhattabi 03-06-2026, 11:18 AM
PercentChangeChart Addon by Deep42 Started by Deep42, 03-06-2026, 12:28 AM	0 responses 40 views 0 likes	Last Post by Deep42 03-06-2026, 12:28 AM
LegToLegProfileModified - Delta - VP - Tick Grouping by TheRealMorford Started by TheRealMorford, 03-05-2026, 06:15 PM	0 responses 43 views 0 likes	Last Post by TheRealMorford 03-05-2026, 06:15 PM
OrderFlow Highlighted Cells by Mindset Started by Mindset, 02-28-2026, 06:16 AM	0 responses 82 views 0 likes	Last Post by Mindset 02-28-2026, 06:16 AM

Announcement

Partner 728x90

Cancelled exit order, since associated position is closed

Cancelled exit order, since associated position is closed

Comment

Comment

Comment

Comment

Comment

Comment

Latest Posts