“History goes back {loaded} days of the {requested} requested” in Senzoukria
When Rithmic serves a history window without error but with no ticks, its archive does not reach further back for that contract and account. Senzoukria reports how many days it really loaded against the range you asked for.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Notice
- “History goes back {loaded} days of the {requested} requested.”
- Range setting
- 1 to 31 days (Trading Settings → History range)
- Kept on disk
- 8 days; beyond that the window is downloaded again on each open
- Cause
- The broker archive for this contract and account
What you see
The chart notice reads “History goes back {loaded} days of the {requested} requested. The broker served the window without an error, so its archive does not reach further back for this contract and account.” The chart itself looks normal, only shorter than the range you chose.
Why it happens
The download reached the end, returned no error code and no bars for the oldest windows. Nothing in the app can know Rithmic’s depth in advance: it varies by firm, account type and month. The app measures it after the fact and says so, instead of drawing a chart half as long as your range without comment.
The range is also bounded on the app side: any whole number of days from 1 to 31. Past 8 days, the local cache no longer keeps the data, so that part is downloaded again every time you open the chart.
How to fix it
- Accept the depth your broker serves, or lower the History range in ⚙ → Trading Settings to match it.
- Check that the contract is the current front month; an older contract may have less history on your system.
- For long backtests, import a folder of Databento exports into the automatic backtest instead of relying on the broker archive.
What it is not
- Not an error: the broker answered without a code.
- Not a cache problem: the chart reports what it really loaded.
- Not fixed by Reload history if the archive stops there; reloading asks the same archive again.
When to contact support
If the problem persists, contact support through Menu → Report a problem, or on the Senzoukria Discord. If another platform on the same login shows older tick history for the same contract, send both ranges and the Rithmic system name.
Related pages
- History could not be completed
- Settings: data cache and history range
- Filling long history for backtests
- Local data cache
In the same section
- Price grid unknown
- Crypto history incomplete
- History loading stalled
- Accepted but no data
- Invalid email or password
- Python engine unavailable
- Databento needs a live licence
- Crypto DOM Profile: no live depth
This page in other languages
Frequently asked questions
- What is the widest history range?
- 31 days. It is the widest window the app will ask a broker for; how far the broker actually goes back depends on your account.
- Why does a 30-day range download again every time?
- Because the local cache keeps 8 days. The part older than that is not stored and must be fetched again when the chart opens.