Orderflow
Placing and managing orders requires tracking the state of an order throughout its lifecycle. Architect presents a normalized view of order lifecycle across all supported venues. Expected state transitions are marked by the diagram arrows. States at the bottom of the diagram are considered final and no further transitions are expected from those states.
Order status descriptions
PENDING
Orders that have been received by Architect begin life as PENDING. Architect will forward the order onto the destination venue/exchange and wait for a reply.
OPEN
The order has been received by the venue/exchange and is considered executable/working.
REJECTED
An order submitted has been rejected by either the Architect OEMS, or the venue/exchange. Inspect the reject reason or reject message to determine the cause of the rejection.
CANCELING
Architect has received a cancel request for this order and is attempting to effect the cancel at the venue/exchange.
CANCELED
An order has been confirmed canceled by the venue/exchange.
OUT
An order is no longer on the orderbook or otherwise considered non-executable by the venue/exchange; e.g. retirement of a DAY order after the end of a the exchange's trading session.
RECONCILED_OUT
Same as the OUT state, except that it was discovered asynchronously by Architect. This might happen in the case of a dropped connection or other downtime event.
STALE
Discretionary state that is assigned to an order by Architect if an expected state transition was not observed past some staleness threshold. Indicates a potential problem with the order at the exchange, or a connectivity issue. Users should contact Architect customer support immediately to gain clarity.
UNKNOWN
Catch-all for unknown order state. Does not indicate a connectivity error; this state will only be observed in the case of unexpected API changes or in beta testing.
Last updated