“The broker refused part of this history request (rp_code 13)” on a Senzoukria chart

What you see

An amber pill in the chart toolbar starting with “⚠ The broker refused part of this history request (rp_code 13).” Hovering it shows the whole sentence: “These refusals are usually intermittent — the chart keeps running on cached and live data, and it retries on its own.” Part of the requested range may be missing on the left of the chart.

Why it happens

History is downloaded from Rithmic’s history plant in windows. When at least one window comes back with rp_code 13, the chart reports it word for word instead of concluding. The app’s rule is explicit: rp_code 13 does not mean you lack a history subscription. On the broker where it was measured, the refusals came and went while logins were accepted. Only when the market is closed and nothing came back does the chart show the market-closed notice instead, because that explanation comes first.

How to fix it

• Wait: the chart retries on its own, and new live bars keep arriving meanwhile.
• If the gap stays, open ⚙ → Trading Settings → Reload history. It re-opens the windows that came back with zero ticks; it clears nothing.
• Close other windows or platforms that load history on the same login at the same time, since the gateway runs one history session per login at a time.
• If every attempt keeps failing over several sessions, ask your broker whether your login may download tick history, quoting rp_code 13 and the time.

What it is not

• Not a verdict on your entitlements: the notice deliberately reports the code without concluding.
• Not a loss of the live feed or of the local cache.
• Not the same notice as “History could not be completed on the last attempts”, which appears after two consecutive empty downloads.

When to contact support

If the steps above do not change anything, send the case from Menu → Report a problem, or ask on the Senzoukria Discord. Give the contract, the history range set in Trading Settings and the time of the notice.