TD-trade-cancelled-when-placing-but-actually-open

QUOTE:
One OCO came back as cancelled.

Tell us more about the setup and result. Symbol, interval, and was the OCO a same bar exit order? Did the OCO stop and limit orders ever show an Active status in Wealth-Lab?

QUOTE:
I opened TDA and found that the first sell order actually went through and is open

What is the "first" order?

QUOTE:
One OCO came back as cancelled.

Tell us more about the setup and result. Symbol, interval, and was the OCO a same bar exit order? Did the OCO stop and limit orders ever show an Active status in Wealth-Lab?

So I had a position in INTC. There was a limit and a stop on the sale for the next day that I was placing later at night, i.e. not a same bar exit and daily quotes. Same for 5 or 6 other positions with other OCO signals in the backtest. I highlighted all the signals (organized by symbol/order type/signal name) and pressed Place Orders.

They all worked (which was great because with Fidelity you had to place each OCO separetly) except the INTC one said Cancelled instead of Active. All the other orders said Active. There was no specific error message or red icon I could click that I could find. It never said Active.

QUOTE:
I opened TDA and found that the first sell order actually went through and is open

What is the "first" order?

The first OCO order on INTC. So the second time I tried it it said I was trying to sell too many shares since the first order actually went through and wasn't Cancelled. I.e. the original OCO INTC order should have said Active not Cancelled.

Sorry for the confusion.

Another occurence today.

This time it's a OCO sale (one of several placed). Stock LMT placed at 10PM. All the others now say active. This one says Placed. I checked TDA and it is actually Active.

I.e. there seems to be a glitch in collecting the status of some orders. There is no refresh button so I don't know how to see if that would change to active because if I close WL to reset, the orders window clears.

And yet another occurence on 10/29. The order said Rejected due to a limit too far from the last price. It even said that on TDA and yet it was executed so re-submitting ended up in a double sized position.

I guess I'll need to pay way more attention and not actually assume it can auto-trade and have to have TDA open as well as WL as it's not clear something WL can fix.

It sounds like the workflow is to place all the orders simultaneously the night before the next session. We'll try to duplicate it and look deeper into the messaging.

Thank you. That's the workflow for the closing of positions yes.

Initiating positions like the last issue, happen through triggers to Place Trades Automatically from the Quotes window. If it looks like an error sometimes I change the errored trade to a market order and re-Place it. It seems like I can't trust the errors right now though so need to double check the positions in TDA. With just a few that's teneble, but if it gets to 20-30 positions that gets more complicated.

This si similar so keeping it on this thread. If you get an error (e.g. price too far) and update the order (e.g. change to market) and place it again, then it executes, the Error message stays and there is still no indication that the trade went through. I did this a couple of times to be sure and it's consistent.

Okay, thanks. I forgot to add a placeholder to investigate this, but I got one now, so we won't forget.

Just an FYI, this keeps happening. Happened on 2 orders I am placing for Monday.

Okay, we're looking into it.

It's going to take some time. It turns out that if you upgrade trading features in a TDA account, you lose the ability to place conditional orders.

Yes, you read that right. If you're trying to place an OCO and see "Error: Conditional Orders are not permitted for accounts in this segment", you need to downgrade your account!

That said and in this so called "upgraded account", a similar problem still occurs when attempting to enter the OCO order. Specifically, when receiving that Error in response to the OCO order, the first child order still goes live.

Thanks.

So far I haven't seen that error but I'll look out for it.