The order lifecycle

Every order SleeveFolio submits (manual or auto-executed) moves through the same lifecycle, mirrored from the broker into your Orders page:

• WORKING: accepted at the broker, waiting to execute
• PARTIAL: some quantity filled, the rest still working
• FILLED: fully executed; the row shows the average fill price next to the quantity that filled
• CANCELLED: pulled before completing, refused outright by the broker, or expired at the end of the trading day — with a reason category showing who ended it: you (per-row or via the kill switch), an automatic safety action, or the broker (a refusal, or an order it expired at day’s end — fully unfilled or with only part of it filled). An order you cancelled directly at the broker outside SleeveFolio still falls under the “you” category, just with no reason text

Each row’s Strategy column names the strategy that placed the order when it came from auto-execute (automatic trading). Orders you placed by hand carry no strategy and show a dash instead.

Duplicate-proof submission

Every order we send carries a fixed ID tag (the client_order_id). If a network hiccup or an automatic retry resubmits the same order, the broker recognizes the tag and refuses to fill it twice: the classic “did my retry just buy twice?” failure can’t happen (in the glossary: idempotent).

POST /v2/orders
{
  "symbol": "AAPL",
  "qty": "10",
  "side": "buy",
  "client_order_id": "<stable per logical order>"
}

The environment tag

Orders record which environment placed them: paper and live history never blend, and cancelling and reconciliation (our routine cross-check against the broker) always talk to the right account, paper to paper, live to live.