Quick answer
What to do first
When NinjaTrader is connected but no market data is moving, check whether the issue is the price server, instrument subscription, data permission, chart state, or provider connection before assuming the strategy logic failed.
- Connected status is not the same as fresh prices and account readiness.
- Frozen charts and stale quotes can leave automated strategies waiting on bad inputs.
- Data-feed monitoring should sit next to reconnect monitoring and strategy restore.
Connected is not the same as ready
NinjaTrader can show a connection while charts, prices, account routing, or strategy inputs are not behaving the way an automated setup needs. For discretionary trading, you may notice the chart is not moving. For automation, the problem can be quieter because the strategy is waiting on data or account readiness.
That gap matters. If a strategy depends on timely market data, order routing, or a stable broker connection, a partially recovered connection can still leave the trading setup exposed to missed signals or delayed decisions.
Use this guide when NinjaTrader appears connected but live prices or market data readiness are the core problem. If the visible issue is one stale chart or one instrument, use the chart-not-updating guide; if the trigger was a named Rithmic or Tradovate reconnect event, use the provider-disconnect guide.
| Condition | What it suggests | First check |
|---|---|---|
| All charts are stale | Broad data-feed or provider readiness problem. | Connection status and provider service status. |
| One instrument is stale | Instrument subscription, symbol mapping, or data permission issue. | Instrument and data subscription. |
| Orders update but prices do not | Price server issue can differ from order server status. | Price feed status and chart updates. |
| Strategy does nothing | The strategy may not be receiving the expected input updates. | Data flow, strategy enabled state, and account connection. |
Common signs of a data-feed problem
The practical signs are usually simple: charts stop updating, quotes freeze, the account appears connected but prices are stale, or a strategy that should evaluate on new data does not act. Some traders also see intermittent disconnects where the platform reconnects before they can diagnose the original problem.
Before assuming the strategy logic failed, check the connection status, instrument subscription, data-feed permissions, and whether the affected account uses the same feed the strategy expects. If the issue is recurring, it is worth treating data readiness as a monitored condition instead of a visual check.
- Chart candles stop printing during active market hours.
- Bid/ask or last price remains stale compared with another feed.
- The connection indicator recovers but strategies still do not evaluate.
- Only one provider, account, or instrument appears affected.
Connected vs usable data checklist
A useful troubleshooting flow separates connection status from data freshness. NinjaTrader can report a provider connection while a specific instrument, permission, or data path is still not delivering usable updates.
This distinction matters most for strategies that evaluate on price changes, ticks, or intraday bars. A stale chart can make a healthy strategy look broken, while the real problem is that the inputs stopped moving.
It also helps avoid unnecessary repair work. If only one instrument is stale, a full platform repair is probably not the first move. If every watched instrument is stale across the same provider, the provider connection or data permission path deserves attention before strategy settings are changed. That keeps the troubleshooting path focused on the smallest likely failure.
Use this when a chart looks frozen even though NinjaTrader is connected.
| Check | What to look for | What it means |
|---|---|---|
| Market/session | The instrument is in an active session and should be printing. | If the market is closed, the chart may be quiet for a normal reason. |
| Timestamp | Last bar, bid/ask, or last price updates during active hours. | A stale timestamp points to data readiness, not strategy logic. |
| Other instruments | Another symbol on the same feed updates normally. | One-symbol issues often point to permission, mapping, or subscription. |
| Other provider/account | A second connection or account behaves differently. | Provider-specific issues should not be treated as full platform failure. |
| Strategy row | The strategy is enabled after the feed stabilizes. | A data issue can cascade into a strategy restore issue. |
Troubleshooting flow for stale prices
- Confirm the market is open for the instrument you are watching.
- Compare the affected chart with another instrument or window.
- Check whether the provider is connected, connecting, or showing a price-server loss.
- Confirm the account and data subscription match the instrument being traded.
- Reload or reopen the affected chart only after you understand whether the issue is local or provider-wide.
- If automation is involved, verify the strategy enabled state after the feed stabilizes.
What a useful data-feed alert should say
A useful alert should not only say that NinjaTrader is online. It should describe the part of the trading session that needs attention: platform launch, provider reconnect, price-server readiness, stale data, or strategy restore.
That specificity helps the trader decide whether the issue is urgent. A frozen chart during active market hours is different from a quiet instrument outside its session, and an order-server issue is different from a price-feed delay.
| Alert wording | Useful when | Why it helps |
|---|---|---|
| Connection restored, waiting for live data | Provider reconnected but chart updates have not resumed. | Prevents assuming the session is ready too early. |
| Market data stale on watched instruments | The platform is open but key symbols are not updating. | Points the trader to data/feed review instead of strategy logic. |
| Strategy restore paused until data updates | Automation should not resume on stale inputs. | Keeps recovery conservative and explainable. |
| Recovery complete | Platform, connection, data, and strategy checks passed. | Gives the trader a concise status summary. |
Why silent feed issues are risky for automation
Automated trading needs a complete chain: NinjaTrader running, the right connection active, live data flowing, account access available, and the strategy enabled. If one part of that chain breaks, the strategy may not behave as intended even though the platform window is still open.
The hardest failures are the ones that do not look like failures. A trader may only discover the issue after a missed entry, a position that should have been managed, or a session where the strategy did nothing because its inputs were not updating.
Useful alerts separate data problems from full platform failures.
| Alert | Means | Why it matters |
|---|---|---|
| Platform recovered | NinjaTrader reopened after a crash or reboot. | The next checks still need connection and strategy readiness. |
| Connection restored | The account or data-feed connection recovered. | Strategy restore can continue after stability. |
| Recovery needs review | The setup is open but a condition is not ready. | The trader can inspect the specific failure instead of guessing. |
Market closed, entitlement issue, or real feed failure?
A no-data report is only useful when it includes context. If the market is closed, a quiet chart may be normal. If one futures contract is not updating while another does, the issue may be contract selection, rollover, or market data entitlement. If every watched instrument is stale during active hours, the provider or data-feed path is the more likely branch.
This is where traders often lose time. They restart NinjaTrader, reload workspaces, or change strategy settings when the real problem is a data permission or price-server condition. Start by narrowing scope, then choose the smallest action that fits the evidence.
For automation, the recovery decision should be explicit: no strategy restore until the data path needed by that strategy is fresh enough to trust. A recovered account with stale prices should trigger a review or wait state, not a full recovered message.
Use these branches before restarting or repairing the platform.
| Branch | What it looks like | Better next step |
|---|---|---|
| Market/session closed | Chart is quiet but session timing explains it. | Do not treat normal market closure as a data-feed outage. |
| Instrument entitlement | One symbol is stale while other symbols update. | Check market data permissions, contract month, and provider subscription. |
| Price-server path | Orders or account state update but chart prices do not. | Treat price feed and order routing as separate readiness checks. |
| Provider-specific issue | Only one connection or account path is affected. | Focus on provider reconnect/status before broad platform repair. |
| Local chart/workspace issue | A second chart or workspace updates but one chart does not. | Reload or rebuild the affected chart only after preserving trading state. |
How Ninja Watchdog helps reduce blind spots
Ninja Watchdog monitors NinjaTrader health beyond the process window. It is built around the conditions that matter for unattended automation: platform recovery, account reconnects, strategy restore, and alerts when recovery needs attention.
For traders using Rithmic, Tradovate, NinjaTrader Brokerage, or another configured connection, the goal is to detect when the setup is not truly ready and keep recovery moving instead of relying on someone to notice a frozen chart.
Example: stale data during an active session
A common morning failure looks like this: NinjaTrader is open, the connection menu no longer shows a full disconnect, but the watched instrument has not printed a fresh bar since the reconnect. The trader may assume the strategy is inactive when the real issue is the data path.
The right alert should describe that distinction. It should not say only that NinjaTrader is running. It should tell the trader that recovery is paused because live data has not resumed for the watched instrument.
This is also useful for support and post-trade review. If the event history shows that NinjaTrader was open but the watched instrument was stale, the trader has a better explanation for why the strategy did not evaluate. That is much more useful than a generic uptime log that leaves the real failure hidden.
FAQ
Common questions
Can NinjaTrader be connected but still have no market data?
Yes. A connection indicator can recover while prices are stale, an instrument lacks data permission, or a price-server path is not ready. Check data flow before assuming automation is healthy.
What should I check first when NinjaTrader charts stop moving?
Check whether the market is open, whether other instruments are moving, whether the provider shows a price-server issue, and whether the data subscription covers the affected instrument.
Why does this matter for automated strategies?
A strategy can remain enabled but fail to act as expected if the live data it needs is stale or missing. The platform window being open is not enough.
Can order routing work while price data is stale?
It can happen that order/account state and price-server state are not the same problem. Treat stale prices as their own readiness check before restoring automated strategies.
Should I reload the chart first?
Reloading can help some local chart issues, but first confirm whether the issue affects one instrument, one provider, or all data. That helps avoid masking the real cause.
Sources
Sources and official references
These references support the platform, provider, and Windows recovery details in this guide. Ninja Watchdog is independent from NinjaTrader.
Protect your setup
Keep NinjaTrader recovery automatic
Start Ninja Watchdog on the Windows computer that runs NinjaTrader and protect automated sessions against crashes, disconnects, strategy downtime, repair issues, alerts, and reboots.