“History could not be completed on the last attempts” in Senzoukria
After two consecutive history downloads that bring nothing back, a Senzoukria chart says so. With broker codes, it prints them unchanged; with no code at all, the usual meaning is an empty archive on that Rithmic system.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- With codes
- “History could not be completed on the last attempts (rp_code {codes}).”
- Without code
- “… the broker returned no status code, which usually means an empty archive on this Rithmic system.”
- Trigger
- Two consecutive downloads that brought nothing back
- Chart state
- Keeps running on cached and live data
What you see
One of two notices in the chart toolbar pill: “History could not be completed on the last attempts (rp_code {codes}). The chart keeps running on cached and live data.” or “History could not be completed on the last attempts — the broker returned no status code, which usually means an empty archive on this Rithmic system. The chart keeps running on cached and live data.”
Why it happens
The history controller counts downloads that end with nothing recovered. After the second in a row it shows this notice. Codes other than 13 are reported as they came, up to four of them; they separate two situations the chart used to confuse: a Rithmic system whose archive is empty for that contract (no code), and a broker that answered something specific (codes). Two firms on the same gateway but on different systems can behave differently here. When the market is closed, the market-closed notice is shown instead, and rp_code 13 has its own notice.
How to fix it
- Check that you are on the current front-month contract; an old contract can have an empty archive.
- Open ⚙ → Trading Settings → Reload history to retry the windows that came back empty.
- Without a code: check that the system you log into offers history for this contract. The same login may be served differently on another system of your firm.
- With codes: send them to your broker as they appear; the app does not translate them into a cause.
- Lower the history range in Trading Settings if you asked for more than your account can serve.
What it is not
- Not a closed market: that case has its own notice and never counts as a failure.
- Not a deleted cache: bars already stored stay on the chart.
When to contact support
Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Include the codes, the contract, the Rithmic system name and whether live bars still arrive.
Related pages
In the same section
- Accepted but no data
- Crypto history incomplete
- Python engine unavailable
- History loading stalled
- Crypto DOM Profile: no live depth
- Invalid email or password
- Databento book refused
- Databento needs a live licence
This page in other languages
Frequently asked questions
- Why wait for two failures before saying anything?
- One empty download can be a passing incident. The notice appears after the second consecutive one, so it describes a pattern rather than a blip.
- What does an empty archive mean?
- The history plant served the request without error and without ticks. The chart treats that as a property of the system and contract, not as a network failure.