Nightly docs
OrderPendingCancel
OrderPendingCancel represents a CancelOrder command having been sent to the trading
venue. The ExecutionEngine applies it to the order, updates the Cache, and publishes
it on the MessageBus. It fires when the system dispatches a cancel request and awaits
venue acknowledgement.
Typical transition: ACCEPTED -> PENDING_CANCEL. Handler: on_order_pending_cancel.
Fields
Beyond the common Python order event fields,
OrderPendingCancel carries:
| Field | Python type | Required/default | Description |
|---|---|---|---|
venue_order_id | VenueOrderId or None | None | The venue-assigned order identifier, if known. |
account_id | AccountId or None | Required | The account associated with the order, if known. |
reconciliation | bool | Required | If generated during reconciliation. |
Example
Reading the event in a strategy handler:
def on_order_pending_cancel(self, event: OrderPendingCancel) -> None:
self.log.info(f"Cancel pending for {event.client_order_id}")Related guides
OrderPendingUpdate
OrderPendingUpdate represents a ModifyOrder command having been sent to the trading venue. The ExecutionEngine applies it to the order, updates the Cache...
OrderUpdated
OrderUpdated records a change to an order's quantity, price, trigger price, or calculated protection price. The execution pipeline applies it to the order...