“⚠ drift N” badge on a NinjaTrader bridge chart in Senzoukria
The drift badge appears when NinjaTrader announced more historical ticks than the bridge delivered to Senzoukria. Tick-based bars such as 100T may not align bar for bar with NinjaTrader for that session; reconnecting retries the history.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Badge
- “⚠ drift {n}” next to the timeframe pills
- Tooltip
- “NinjaTrader announced {expected} historical ticks for {symbol}, but only {received} were received…”
- Consequence
- 100T bars may not align bar for bar with NinjaTrader for this session
- Fix
- Reconnect to retry
What you see
A small “⚠ drift {n}” badge next to the timeframe pills, where n is the number of missing ticks. Its tooltip reads “NinjaTrader announced {expected} historical ticks for {symbol}, but only {received} were received. 100T bars may not align bar-for-bar with NT’s chart for this session — reconnect to retry.” The status bar keeps showing LIVE.
Why it happens
The bridge protocol starts with a header that announces how many historical ticks NinjaTrader will send, followed by the ticks and an end-of-history marker. When fewer ticks arrive than announced, Senzoukria records the difference instead of hiding it. Count-based bars are the most sensitive: a single missing tick shifts where every following 100-tick bar closes, while the live part of the session keeps flowing normally.
How to fix it
- Reconnect the bridge: a new backfill starts, the drift badge is cleared, and the history is sent again.
- Keep the NinjaTrader chart’s loaded range reasonable. The bridge only replays what that chart has loaded, and a very long 1-tick chart strains NinjaTrader; the indicator recommends a 100 Tick chart with Tick Replay on.
- If you compare Senzoukria and NinjaTrader bar for bar, compare time-based bars, which are not shifted by a missing tick in the same way.
What it is not
- Not the “NT misconfigured” banner, which is about the missing sequence counter or Tick Replay.
- Not a loss of live data: the badge concerns the historical batch of the current session.
- Not a reason to wipe the chart: a new backfill merges by bar and replaces bars where it is more complete.
When to contact support
If the problem persists, contact support through Menu → Report a problem, or on the Senzoukria Discord. Copy the tooltip numbers (announced and received) and the instrument, and say how much history the NinjaTrader chart had loaded.
Related pages
In the same section
- History load already running
- Already subscribed (1029)
- Subscription required or expired
- GEX key required
- Alpaca unauthorized
- Anthropic refused this key
- NinjaTrader bridge stuck connecting
- Databento book refused
This page in other languages
Frequently asked questions
- Does drift affect 1-minute bars?
- The warning targets tick-based bars. Missing historical ticks still reduce the volume of the bars they belonged to, so a reconnect is the clean fix for any comparison.
- Does the badge disappear by itself?
- It is cleared when a new history replay starts, which happens when the bridge reconnects.