“You are reading local data, not the live market”: the Local data badge
With no broker connected, a Senzoukria chart opens on the history already stored on the machine and wears a “Local data” badge. It scrolls and computes as usual but does not advance; live ticks, the order book and the bar in progress need a broker.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Badge
- “Local data” — “No broker connected — this chart is drawing history already stored on this machine.”
- Notice title
- “You are reading local data, not the live market”
- Works offline
- Footprint, volume profile, indicators, drawings and Replay
- Needs a broker
- Live ticks, the order book, the DOM and the bar in progress
What you see
A blue “Local data” badge in the chart toolbar and a notice: “No broker is connected, so the chart opened on the history already downloaded to this machine. It scrolls, zooms and computes exactly as usual — it simply does not advance.” It states how far the data goes (“Local data goes up to {date} at {time} ({zone}).”), the age of the last cached bar and the number of bars cached on the timeframe, then: “This is not a connection failure and nothing is missing.”
Why it happens
The chart reads the local cache first, so it can draw without any connection. When no broker is connected, that cache is all there is. The notice exists because a chart without a live feed and a broken chart look the same.
How to fix it
- Click “Connect a broker” to open the Connection Manager, or “Guide me step by step” for the five-step connection guide.
- Once a broker connects and the chart receives live data, the Local data badge and the notice go away.
- If you only want to study, click “Replay a cached session” or “Hide this notice” and keep working on the local history.
What it is not
- Not missing data: the notice states what is cached and how old it is.
- Not a broken connection when you never connected: the app did not try to reach a broker.
- Not the same as “No local data for {symbol}”, which means there is nothing stored at all for that instrument.
When to contact support
If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Only if the badge stays after a broker shows as connected: include the connection card state and the chart’s data source.
Related pages
- No history before the first broker login
- Offline chart and weekend behaviour
- Step-by-step connection guide
- Local data cache
In the same section
- AI model unreachable
- Trading disabled on the connection
- Backtest import from Databento
- Tradier token check failed
- Big Trades not showing
- This screen stopped
- Diagnostic: session already running
- Maximum number of machines
This page in other languages
Frequently asked questions
- How long is local history kept?
- The chart cache keeps 8 days of intraday history; sessions downloaded for Replay are kept separately as sessions on disk.
- Can I place orders from a Local data chart?
- Orders need a broker connection and an account feed. The notice lists the DOM and live ticks among what needs a connected broker.