Cannot enable Strategy if I do CancelAllOrders(order.Instruments) in State.DataLoaded

[localappleseed]

I plan to cancel all existing pending orders when my Strategy starts. The following code will prevent me enabling Strategy (I cannot click to enable the Strategy).

if (State == State.DataLoaded)
{
foreach (Order order in myAccount.Orders)
{
myAccount.CancelAllOrders(order.Instrument);
}
}

If I move the above code to under (State == State.SetDefaults), then it works fine. It can cancel all pending orders and start my strategy. But putting under SetDefaults, it is dangerous, because it can be triggered when I start any other Strategies.

Is there a way to do this under State.DataLoaded and still can enable Strategy?

[NinjaTrader_ChelseaB]

Hello localappleseed,

Are there errors appearing in the Log tab of the Control Center when trying to enable the strategy?

If so, what are the errors?

[localappleseed]

There is no error, nothing from logs either. Here are the steps to reproduce:
From NT control -> Strategies -> Right Click to select New Strategies -> Select my Strategy -> When my strategy is shown, from right side there is little square which I should be able to click to enable the Strategy, but I cannot click it, it doesn't respond.

[NinjaTrader_ChelseaB]

Hello localappleseed,

Is the Account selection grayed out or can this be manipulated?

Is the account connection connected?

Can you select that account in the Account drop-down of the SuperDOM?

Has this instance of the script been enabled at least once on a different account?
If you create a new instance with the correct account selected in the parameters the first time, is the behavior the same?

[localappleseed]

As you can, the red circled is the place where I tried to enable. It doesn't allow me to enable until I move the code to SetDefaults.
So answer your question, 1) it it not grayed, cannot be manipulated; 2) yes, connected, because it works fine when I move the code; 3) yes, I can select account of SuperDOM; 4) not tried in different account, but from the same account, I can make it work only moving the 2 lines of code to SetDefaults. 5) the behavior has no difference.

This is NOT working:

if (State == State.DataLoaded)
{
foreach (Order order in myAccount.Orders)
{
myAccount.CancelAllOrders(order.Instrument);
}
}

This is working;

if (State == State.SetDefaults)
{
foreach (Order order in myAccount.Orders)
{
myAccount.CancelAllOrders(order.Instrument);
}
}

[NinjaTrader_ChelseaB]

Hello localappleseed,

If the account selection is not being changed on a strategy then I would expect an error in the Log tab of the Control Center.

So far it's been one or the other and I haven't seen any other reasons that would immediately disable a strategy to date, but I would be extremely interested.

Are you doing a check for null to make sure the account is not null?
When and with what code are you getting an account object?

Print 'myAccount is not null' to the output window in State.DataLoaded from a condition checking for null before the code causing the script to crash without an error message.

Include the output with your reply.

[localappleseed]

Everything is the same except I changed one word in the code, see below. Everything including testing procedure, loading data, strategy etc are the same.
There is no null involved here, as I don't get running error. Nothing printed in logs.
I am not sure how I answer your question, as I said, only for following line can change the behavior, working or not working. I already narrowed the problem to one line of code. Please help if you can, thanks.


from
if (State == State.DataLoaded) // <<<< I cannot enable Strategy
to
if (State == State.SetDefaults) //<<<<< I can enable Strategy

[NinjaTrader_ChelseaB]

Hello localappleseed,

May I have a screenshot of the Log tab of Control Center after you have attempted to enable the script so that I may confirm there are no error messages?