“replay load failed: the broker denies tick history on this account (rp_code 13)”

A Replay session that is not on disk is downloaded tick by tick from Rithmic’s history. When the broker answers rp_code 13 during that download, Senzoukria stops and says the broker denies tick history on this account; a history login refusal has its own message.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Message
“replay load failed: the broker denies tick history on this account (rp_code 13)”
Login refusal
“replay load failed: broker rejected the history login (codes: …)”
Transport
“replay load failed: history transport error (…)”
Where
Replay → Prepare, under the session picker

What you see

After “Load session”, the Replay screen shows the error in red: “replay load failed: the broker denies tick history on this account (rp_code 13)”. Related failures read “replay load failed: broker rejected the history login (codes: …)” or “replay load failed: history transport error (…)”. If the market is open, the “Provider unavailable” card may appear below.

Why it happens

A session already on disk loads without any broker. Otherwise, the app drains the whole CME session (17:00 CT the evening before to 16:00 CT) from Rithmic’s history plant, using the credentials of your default Rithmic connection. If any window of that download answers rp_code 13, the load stops with this message. The history login is separate from the live login, so an account can stream live data and still be refused history.

How to fix it

  • Retry later: on chart history, rp_code 13 refusals were measured as intermittent.
  • Pick a session listed among the sessions on disk; it loads with no broker.
  • Import the day from Databento export files: imported sessions replay without any login.
  • If every day is refused, ask your broker whether your login may download tick history, quoting rp_code 13.

What it is not

  • Not a closed market: that case reads “no ticks for {day} — market closed that day, or nothing archived”.
  • Not a problem with sessions already on disk.

When to contact support

Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Include the contract, the day, and the exact line including the codes.

In the same section

This page in other languages

Frequently asked questions

Why does the live chart work while Replay is refused?
Replay downloads from the history plant, which has its own login and permissions. A live subscription says nothing about history access.
How long does a first load take?
The Replay screen notes that a full session is a few million ticks and that the first load takes 30 to 60 seconds.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.