nautechsystems/nautilus_trader · error

actual order ID mismatch: expected {expected_actual_order_id

Error message

actual order ID mismatch: expected {expected_actual_order_id}, was {}

What it means

Error "actual order ID mismatch: expected {expected_actual_order_id}, was {}" thrown in nautechsystems/nautilus_trader.

Source

Thrown at crates/adapters/binance/src/futures/http/models.rs:1608

    #[expect(clippy::too_many_arguments)]
    pub fn to_order_status_report_with_actual(
        &self,
        actual: &BinanceFuturesOrder,
        account_id: AccountId,
        instrument_id: InstrumentId,
        price_precision: u8,
        size_precision: u8,
        treat_expired_as_canceled: bool,
        ts_init: UnixNanos,
    ) -> anyhow::Result<OrderStatusReport> {
        let expected_actual_order_id = self
            .actual_order_id
            .as_deref()
            .filter(|id| !id.is_empty())
            .context("algo order has no actual_order_id")?;

        if expected_actual_order_id != actual.order_id.to_string() {
            anyhow::bail!(
                "actual order ID mismatch: expected {expected_actual_order_id}, was {}",
                actual.order_id
            );
        }

        if self.symbol != actual.symbol {
            anyhow::bail!(
                "actual order symbol mismatch: expected {}, was {}",
                self.symbol,
                actual.symbol
            );
        }

        if self.side != actual.side {
            anyhow::bail!(
                "actual order side mismatch: expected {:?}, was {:?}",
                self.side,
                actual.side

View on GitHub (pinned to a4b06ed870)

When it happens

Trigger: Thrown at crates/adapters/binance/src/futures/http/models.rs:1608 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of nautechsystems/nautilus_trader@a4b06ed870 (2026-08-16). Data as JSON: /api/errors/8577cea757b04d19. Report an issue: GitHub.