Problem summary
After the regular session close on Thursday, June 18, 2026, my automation called PATCH /v2/orders/{id} (replace_order) to raise an OCO limit target. The replace never completed. The old order remains in pending_replace and the replacement order remains in new. Both OCO parents appear to share the same stop leg (held), so all 13 shares show as unavailable. It is very frustrating since it is stuck and disturbing my strategy and I am stuck with it.
@Sameh_Nashed what is the paper account number and ideally the original order number. I can do some checking and see what the issue may be.
Hi Dan,
Thanks a million the stuck order was solved yesterday. But I really appreciate your follow up.
If I come across any other issue I’ll certainly reach out to you.
Much appreciated.
Regards
Sameh Nashed