Order Lifecycle
Every broker order sent through TickMint is tracked by an order state machine in the local gateway. It decides which status you see in the Trading Dock, on the chart and on the DOM, and it is designed never to show an order as finished unless the broker says it is.
Lifecycle stages
An order moves forward through four stages and never goes back:
| Stage | Meaning |
|---|---|
| Pending submit | TickMint has sent the order and is waiting for the broker to accept it. |
| Acked | The broker accepted the order. |
| Working | The order is live at the exchange. |
| Done | Terminal: filled, cancelled, rejected, or no longer known to the broker. |
On top of the stage, the order can carry temporary flags:
- Pending modify: a price or quantity change has been sent and not yet confirmed.
- Pending cancel: a cancel has been sent and not yet confirmed.
- Cancel queued: you cancelled before the broker had acknowledged the order. TickMint holds the cancel and sends it as soon as the acknowledgement arrives.
- Trigger pending: a stop or conditional order is waiting for its trigger.
Statuses you see
The displayed status is chosen in this priority order (the first rule that matches wins):
| Priority | Condition | Status |
|---|---|---|
| 1 | Done | FILLED, CANCELLED, REJECTED or UNKNOWN |
| 2 | Pending cancel or cancel queued | PENDING_CANCEL |
| 3 | Pending submit | PENDING_SUBMIT |
| 4 | Pending modify | PENDING_MODIFY |
| 5 | Some quantity filled | PARTIALLY_FILLED |
| 6 | Acked, not yet working | ACKED |
| 7 | Trigger pending | TRIGGER_PENDING |
| 8 | Otherwise | WORKING |
The Orders & Fills tab simplifies these to SUBMITTING, WORKING, PENDING_CANCEL, FILLED and CANCELLED.
Rules that keep the status honest
- Done only on broker confirmation. An order becomes Done only when the broker reports it complete, or when a request definitively fails. A timeout or a lost connection never marks an order as done; instead the dock shows its last known state with
· STALE. - Late fills still count. After an order is Done, fill reports that arrive late are still applied. Fills are de-duplicated by fill ID, so a repeated report is never counted twice.
- OCO siblings. When one side of a bracket fills and the broker cancels the other, the sibling goes straight from Working to Done.
- Failed modify or cancel. If the broker rejects a modify or cancel, the pending flag is cleared, the order stays as it was, and the error is kept with the order.
- Rejections. A rejection report that does not end the order stores the reject reason without closing the order.
- Reconnect recovery. After a reconnect, TickMint loads a snapshot of open orders from the broker. Any in-flight modify or cancel is cleared, because the snapshot is the truth. An order that is missing from the snapshot is marked Done with status
UNKNOWN. If an order completes as unknown but its full quantity was filled, it is shown asFILLED.
Rapid modifications
When you drag an order line on the chart, TickMint can generate many price changes per second. The gateway keeps only the latest requested price while a modify is in flight and sends it once the previous one is confirmed, so the broker sees a short sequence of modifies rather than one per pixel.
Orphaned brackets
If your position is flat but a bracket order (take profit or stop) is still working at the broker, the dock flags it as ORPHAN. Cancel it so it cannot open an unintended position.