> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/concepts/orderflow.md).

# 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.

<figure><img src="/files/bs1yfJ5hYkfasiBNp6nh" alt=""><figcaption></figcaption></figure>

### Order status descriptions

<table><thead><tr><th width="187.44140625">Order Status</th><th>Description</th></tr></thead><tbody><tr><td>PENDING</td><td>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.</td></tr><tr><td>OPEN</td><td>The order has been received by the venue/exchange and is considered executable/working.</td></tr><tr><td>REJECTED</td><td>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.</td></tr><tr><td>CANCELING</td><td>Architect has received a cancel request for this order and is attempting to effect the cancel at the venue/exchange.</td></tr><tr><td>CANCELED</td><td>An order has been confirmed canceled by the venue/exchange.</td></tr><tr><td>OUT</td><td>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.</td></tr><tr><td>RECONCILED_OUT</td><td>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.</td></tr><tr><td>STALE</td><td>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.</td></tr><tr><td>UNKNOWN</td><td>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.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.architect.co/concepts/orderflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.