Skip to content

Rust IB adapter: execution client venue IB never matches instrument venue SMART, so every stock order is denied locally #4983

Closed

Description

@achimcc

Version: v1.227.0 (Rust, nautilus-interactive-brokers)

What happens

Submitting a market order for a stock through the Rust Interactive Brokers adapter is
denied by ExecutionEngine before it reaches IB:

OrderInitialized(instrument_id=AAPL=STK.SMART, client_order_id=O-..., side=BUY, type=MARKET, quantity=1)
[CMD]--> SubmitOrder
WARN OrderDenied(instrument_id=AAPL=STK.SMART,
                 reason='Order venue SMART does not match client venue IB')

The connection itself is healthy: data client connects, account state is reconciled
(Received 0 order(s), 0 fill(s), 0 position(s)), historical daily bars are returned
(251 bars for AAPL over one year), and the instrument resolves through the provider.

Why

Two halves of the same adapter disagree, and the engine compares them unconditionally:

  • crates/adapters/interactive_brokers/src/common/parse.rs:70
    SecurityType::Stock => Venue::from("SMART") — every stock instrument gets venue SMART.
  • crates/adapters/interactive_brokers/src/factories.rs:166
    the execution client is constructed with *IB_VENUE, i.e. venue IB.
  • crates/execution/src/engine/mod.rs:1749-1755
    handle_submit_order denies whenever order.instrument_id().venue != client.venue(),
    with no exception for multi-venue brokers.

The Python adapter does not have this problem because its execution client is registered
without a venue:

  • nautilus_trader/adapters/interactive_brokers/execution.py:209
    venue=None, # Multi-venue broker - route by account_id instead

In Rust, ExecutionClientCore (crates/execution/src/client/core.rs:42) declares
pub venue: Venue — not Option<Venue> — so the venue-less client that Python relies on
cannot be expressed.

Reproducing

crates/adapters/interactive_brokers/examples/node_exec_tester.rs already uses the
failing combination out of the box: InstrumentId::from("AAPL=STK.SMART") (line 74),
ClientId::new(IB) (line 118), add_exec_client(None, ...) (line 108). Running it
against a paper account with ReadOnlyApi=no reproduces the denial.

Not a configuration problem

symbology_method only changes the symbol part of the instrument ID.
convert_exchange_to_mic_venue / symbol_to_mic_venue can replace SMART with a MIC
code, but never with IB.

Why the existing escape hatches do not help

ExecutionEngine::execute_command already resolves the client three ways — explicit
command.client_id(), then routing_map by venue, then default_client
(engine/mod.rs:1671-1679). All three lead into handle_submit_order, which then denies
on venue inequality regardless of how the client was found. So naming the client
explicitly, or routing SMART to it, does not help.

Suggested direction

Making ExecutionClientCore::venue an Option<Venue> would ripple through the
ExecutionClient trait and every adapter. A smaller, additive change expresses the same
intent:

// crates/common/src/clients/execution.rs
pub trait ExecutionClient {
    // ...
    /// Whether this client serves instruments across multiple venues.
    fn is_multi_venue(&self) -> bool { false }
}

…overridden to true by the IB execution client, and used to guard the two venue checks
in engine/mod.rs (lines 1751 and 1813). That keeps the check where it protects
venue-routed clients and lifts it only where the broker is genuinely multi-venue — the
same distinction the Python adapter draws with venue=None.

Happy to open a PR if that direction is acceptable.

Activity

  1. cjdsellers commented on Oct 4, 2026

    @cjdsellers
    Member

    Hi @achimcc,

    Thanks for the clear report. This was fixed by #4129, which shipped in 1.228.0 and is in the v2 release candidates: the IB execution client now accepts orders for instruments on exchange venues such as SMART, so upgrading should resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions