Chart notices: busy, incomplete and refused history
Senzoukria charts report what the data path is doing through short notices: a busy history load, a partial or refused history request, a stalled download, a closed market, plus a status bar and a live banner that tell you where the chart stands.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Floating stack above the crypto chart; notice badge in the Rithmic chart toolbar; status bar and live banner on every footprint chart
- Closing a notice
- Click × ; a hidden warning or error leaves a ⚠ pill while its cause lasts
- Stall watchdog
- 120 s without any progress event during the broker download
- Busy retry
- One automatic retry after 3 s
What it does
A chart notice is a sentence about the data, never a verdict about your account. The history controller reports what the broker said: which spans were refused, which came back empty, whether another load already holds the instrument, or whether the market is simply closed. The chart keeps running on cached and live data while a notice is displayed.
On the crypto chart, notices are a floating stack. Each one has a tone (info, warning or error), optional action button and a × button. A closed notice does not come back while its text merely progresses; it returns only if its identity changes, for example a new pair, a new timeframe or a new list of missing days. A closed warning or error whose cause is still present leaves a small ⚠ pill with a count; clicking the pill reopens them.
On the Rithmic chart, the current notice is a badge in the chart toolbar; hovering it shows the full text. The badge is hidden while the history loader overlay is on screen.
Notices
| Notice | Trigger | What to do |
|---|---|---|
| CME Globex is closed (weekend or daily pause) | The download returned nothing and the CME clock says the market is closed | Nothing. Cached sessions stay on the chart and can be replayed; new history arrives when the market reopens. |
| The broker refused part of this history request (rp_code 13) | At least one span answered with rp_code 13 | Wait: these refusals are usually intermittent and the chart retries on its own. |
| History could not be completed on the last attempts (rp_code …) | Two consecutive downloads brought nothing back and the broker returned codes | Reload history from ⚙ → Trading Settings if it persists; the chart keeps running on cache and live. |
| … the broker returned no status code | Two consecutive empty downloads with no code, typically an empty archive on this Rithmic system | Check that the system you log into offers history for this contract. |
| This instrument's price grid is unknown | The download worked but nothing was cached because the tick size is unknown | Add the tick size to the instrument catalogue; until then history is re-downloaded on every load. |
| Another history load is already running for this instrument | Another ensure holds the instrument, usually the same contract open in a second window | Nothing at first: one retry runs after 3 s. If the wording changes to still running, close the other window then use Reload history. |
| History loading stalled | 120 s without a single progress event during the download | The gauge closes on what cache and live already have. Use ⚙ → Trading Settings → Reload history. |
Status bar and live banner
The status bar shows a connection dot (Busy, Connected or Disconnected), the symbol, the timeframe, the source label, the last price, the session delta since 00:00 local, the session volume, the trade count and a countdown to the next bar close. Bridge sources that push an exchange daily volume show it next to the locally captured total. The countdown disappears on count-based bars such as 100t, which do not close on the clock.
Connection states used across the app are LIVE, CONNECTING, RECONNECTING, ERROR, IDLE, CONNECTED and No broker.
When you scroll away from the latest bar, a small banner labelled Historique appears with two buttons: → Live returns to the newest bar and resumes vertical centring; ↺ Scale resets the zoom.
Limits or pitfalls
Read notices for what they say:
- rp_code 13 does not mean you lack a history subscription. Measured on one broker, refusals were intermittent while logins were accepted; the notice deliberately reports the code without concluding.
- Session counters in the status bar start at local midnight, not at the exchange session open, so they differ from a broker's session figures on overnight trade.
- Notices never clear the cache or the live feed. Reload history re-opens spans that came back empty; it does not delete anything.
Related pages
- History loading screen
- Offline chart and weekend behaviour
- Rithmic footprint software
- Cumulative delta explained
This page in other languages
Frequently asked questions
- I closed a warning and a ⚠ appeared. What is it?
- The cause of the warning is still present. The pill keeps a data gap from becoming invisible; click it to reopen the hidden notices.
- Where is the Reload history button?
- Chart → ⚙ Settings → Trading Settings → Reload history. It re-requests windows the broker drained to zero ticks and closes the modal so the progress paints on the chart.
- The status bar says Disconnected but the chart still moves. Why?
- The dot reflects the connection of the chart's own data path. Cached bars and Replay still render without a live connection; live ticks, the order book and the bar in progress need a connected broker.