NinjaTrader recovery tools compared: restart, reconnect, and strategy restore

Match the tool to the interruption

A process monitor detects a closed application. A connection monitor detects a lost provider session. A data watchdog detects missing ticks while the connection still appears active. Restoring a strategy is a further operation after the platform and connection return.

The distinctions below come from official vendor documentation checked October 8, 2026. Ninja Watchdog publishes this comparison. We have not run a comparative recovery-speed or reliability test; an undocumented capability remains unverified.

Documented recovery features

What has to remain available for recovery

Ninja Watchdog runs as a Windows application with a small NinjaTrader bridge add-on. The bridge needs authorization when NinjaTrader requests it, including after an add-on change. It does not require edits to strategy code, parameters or workspaces. Cloud monitoring can report a missing computer check-in, but the computer still needs to be available for local recovery.

HeartBeat describes monitoring-only operation and opt-in recovery. Its documented checks include current state, cooldown and attempt limits. An interactive desktop is a specific dependency for its NinjaTrader UI recovery; a scheduled NinjaTrader restart does not establish recovery after a Windows or VPS reboot.

GFREQ WatchDog runs outside NinjaTrader and watches its logs and process. The documented NT8 Live reconnection uses Windows UI Automation and a confirming log event. A process relaunch and optional login fill do not, on their own, establish which strategies will be enabled afterward.

CrossTrade stale-data detection and retry limits

CrossTrade Data Watchdog subscribes to a reference instrument for each monitored connection, normally the front-month ES contract. It compares time since the last tick with a configurable timeout, documented as 60 seconds by default. Checks pause outside the market session, so a closed market is not treated as a stalled feed.

When Auto-Reconnect is enabled for the same connection, Data Watchdog detects stale data and initiates a disconnect; Auto-Reconnect supplies the reconnection delay, retry budget and deduplication guards. Data Watchdog does not maintain a second attempt counter in that combination. Without Auto-Reconnect enabled, the documentation says it uses its own recovery loop with the same maximum attempt limits.

The Auto-Reconnect page specifies a default 10-second delay and stops after five failed attempts. Connecting manually or re-enabling Auto-Reconnect resets its counter. It also says intentional manual disconnects are left alone. Those controls are relevant when comparing an unexpected drop with a deliberate disconnect test.

This distinction affects configuration: inspect both features for the same connection rather than assuming that two enabled recovery features provide two independent retry budgets. The reference instrument is a signal for that connection; it does not establish that every chart, account or strategy has resumed. Because this feature runs inside the NT8 add-on, its page does not establish relaunch of a stopped NinjaTrader process.

Check positions when a strategy restarts

NinjaTrader Start Behavior determines how a strategy handles its calculated position and the account position when it starts. Some synchronization options can submit orders. A strategy enabled again after recovery can therefore resume trading under its own settings, even if the recovery tool does not directly place orders.

Compare the exact account, instrument, strategy instance, working orders and start setting before and after a simulation interruption. An enabled state is one observation; matching the intended position and order state is a separate observation.

Questions that distinguish the recovery paths

Use the simulation observation record in the recovery guide to answer these questions for your own configuration. Product pages establish advertised scope; an actual interruption test establishes only the behavior observed in that setup.