Tradovate reconnect in NinjaTrader: verify the account and strategy

Check the connection type and trading mode behind the name

Tradovate’s Desktop guide specifies NinjaTrader as the connection type in Multi-provider mode. The saved connection initially appears as My NinjaTrader, but its name can be changed. A label such as Tradovate is therefore a user-chosen name, not proof of the configured account or environment.

Open Connections > configure and inspect the relevant saved connection. Match its username and Live or Simulated mode to the account you intend to use. For a prop or evaluation account, follow that provider’s connection instructions; do not infer the required mode from the word “funded.”

Tradovate documents Multi-provider mode for using a Tradovate account alongside an evaluation-service account. Enabling it requires a NinjaTrader restart before configuring the additional connections. Changing that setting is a setup step, not a general cure for every disconnect.

Inspect the intended account without hiding relevant orders

In the Control Center Orders tab, use Filter By Account to isolate the affected account. Check Filter Orders too: Active Orders alone cannot show an order that has already filled or been rejected. Select the view needed for the interruption you are investigating.

NinjaTrader distinguishes Account Display Name from Account Name; the two can differ for live brokerage accounts. Account Name is an optional grid column available through Properties. Compare it with the intended account instead of relying only on a familiar display label.

Review the instrument, order ID, State, Filled and Remaining quantities. The Strategy column can help identify which ATM or NinjaScript strategy submitted an order. A reconnect message cannot tell you whether a particular order filled, stayed working or was rejected.

The documented Orders grid covers the current day. For an interruption spanning midnight, include the earlier records rather than treating an empty current-day view as the complete history.

A working chart may use another connection

With multiple connections, NinjaTrader can obtain market data from a different provider than the account used for orders. Preferred real-time and historical data connections also affect that selection. A moving chart therefore supports a data-feed observation, not proof that your Tradovate account is ready.

If the account has returned but the instrument is stale, follow the separate feed and subscription checks. If prices are current but the account or orders remain unclear, keep the investigation on the account path.

Separate account recovery from strategy restart

NinjaTrader’s connection-loss handling determines what a running strategy does during a disconnect. Stop Strategy takes no restart action when the connection returns. Recalculate has separate stop and restart conditions. Record the affected instance’s outcome rather than assuming every strategy follows the connection back online.

Before re-enabling, compare the account’s actual position and working orders with the strategy’s expected state. Start Behavior controls startup handling; synchronization can submit orders and does not guarantee continuing alignment. Use the dedicated guides for those settings.

What Ninja Watchdog adds

Ninja Watchdog can attempt account reconnection and restoration of eligible previously running strategies when the required environment is available. Its Windows app works with the NinjaWatchdogBridge add-on installed in NinjaTrader. Recovery does not replace checking account identity, orders or position alignment.

Recovery email alerts are available today; SMS and WhatsApp alerts are coming soon. Keep the reported recovery event separate from confirmation of the intended account and strategy outcome.