OrderDeniedCopy Anchor Link

OrderDenied records that the Nautilus system cannot submit an otherwise valid order, for example because of a risk limit or an unsupported feature. The execution pipeline applies it to the order, updates the Cache, and publishes it on the MessageBus.

The risk engine, execution engine, execution algorithms, and execution clients can all deny an order.

Typical transition: INITIALIZED -> DENIED. Handler: on_order_denied.

FieldsCopy Anchor Link

Beyond the common Python order event fields, OrderDenied carries:

ExampleCopy Anchor Link

Reading the event in a strategy handler:

def on_order_denied(self, event: OrderDenied) -> None:
    self.log.warning(f"Order {event.client_order_id} denied: {event.reason}")

Related guidesCopy Anchor Link

• Events - Event categories, dispatch, and the common order event fields.
• Execution - Risk checks and the pre-trade pipeline.
• Order denied reasons - The standardized code set and message forms.
• Orders - Order types and the state machine.