nautechsystems/nautilus_trader · error

actual order symbol mismatch: expected {}, was {}

Error message

actual order symbol mismatch: expected {}, was {}

What it means

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

Source

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

        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
            );
        }

        let mut report = self.to_order_status_report(
            account_id,
            instrument_id,
            price_precision,

View on GitHub (pinned to a4b06ed870)

When it happens

Trigger: Thrown at crates/adapters/binance/src/futures/http/models.rs:1615 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/ece4ae55f08a3240. Report an issue: GitHub.