For example from web account orders dashboard:
Using alpaca-py paper trading expected PARTIALLY_FILLED not CANCELED
For example from web account orders dashboard:
Using alpaca-py paper trading expected PARTIALLY_FILLED not CANCELED
@kniyotai The order status is the last status of the order. In the background, the field is overwritten each time the status changes. For example, it starts as accepted
, then is updated to new
, then perhaps partially_filled
, then typically filled
. It will always end with one of the following terminal statuses:
FILLED
CANCELLED
EXPIRED
REJECTED
REPLACED
DONE_FOR_DAY
SUSPENDED
CALCULATED
Since the order was Immediate Or Cancel (IOC) it partially filled but then was cancelled and therefore had a final state of CANCELLED.
Thank you dan, i am able to pool and follow the sequence of states but never got to that elusive partially_filled ,
So the only real indication for partial feel is the actual filled quantity followed by cancelled on IOCs, which is somewhat confusing but works…
I imagined the partially_filled would also be a worthy terminal state.
Thanks.