NinjaTrader chart not updating while connected: chart, session and contract checks

First, bring the current bar back into view

A chart can keep receiving data while you are looking at older bars. Click the chart, then press End to return to its current bar, or use the return icon at the top right when it appears. Compare the latest timestamp with the same contract in another window.

If the price axis shows an F button, its scale is fixed. Click F to restore automatic scaling. New prices outside a fixed visible range can look like a frozen display even though data continues to arrive.

Use a matching price source for the comparison. A changing bid or ask alone does not establish that a new trade occurred. For prices that are stale across windows, check the selected provider and subscription using the feed guide.

Inspect the affected Data Series

Right-click the chart and open Data Series. On a chart with multiple series, select the affected one in Applied before inspecting its settings.

No new bar can be normal for this session or bar type

Trading Hours templates exclude data outside their defined sessions. An RTH chart can stop adding bars outside its regular session while another chart using extended hours continues. In the Trading Hours window, inspect the selected template's time zone, session boundaries and holiday overrides. Match those settings in your comparison; do not change a strategy's session merely to make a diagnostic chart move.

Tick bars require a specified number of ticks, volume bars accumulate traded volume, and range bars require the configured price movement. None promises a new bar every minute. Watch the current bar and its underlying data before treating a pause between completed bars as a fault.

Check the contract month in each window

Two windows labelled with the same futures root can use different expiries. Compare the complete instrument name, especially around rollover. An older contract with little activity is not a useful reference for the active contract.

NinjaTrader supports changing a window's expiry individually. Its batch rollover updates eligible instruments across open workspaces, but NinjaScript strategies are not rolled forward automatically. A changed chart therefore does not prove a strategy now uses that contract. Review the strategy's own input and account before restarting it.

Use a simple chart to isolate custom components

Create a separate comparison chart with the same contract, price type and session, a standard bar type, and no optional indicators or chart template. If it updates, compare the original chart's custom bar type, indicators and template one at a time. Keep live automation on its existing configuration while you isolate the display symptom.

Excessive history and custom scripts can also slow a chart. NinjaTrader's performance guide recommends reducing unnecessary historical loading and isolating scripts. Do not change a live strategy's calculation mode just to improve the diagnostic chart.

If current prices arrive but one configuration repeatedly stalls, capture that configuration and its timestamp for the component developer or NinjaTrader support. A single frozen chart does not by itself justify clearing a database or restarting every strategy. After a change, check for continuing new input; refreshed historical bars alone do not confirm live updates.