“The broker refused tick history on this account (rp_code 13)” when rebuilding bubbles

What you see

After clicking “Rebuild {depth} on {symbol}”, the message under the button reads “The broker refused tick history on this account (rp_code 13). Nothing could be rebuilt beyond this point.” Other outcomes are “Done — {rows} bubbles rebuilt over {depth}. They are already on screen.”, the busy message, or “Failed: {error}”.

Why it happens

The rebuild requests the ticks from the broker again, then writes only bubbles; candles already in the cache do not move. Rithmic answered with rp_code 13 on that tick history request, so the rebuild stopped where the refusal occurred. As for chart history, the app reports the code as the broker sent it and does not turn it into an entitlement verdict.

How to fix it

• Try a shorter depth first (24 h), which asks for far fewer ticks.
• Wait for any chart history download on the same contract to finish; only one history load runs at a time.
• Run long rebuilds outside session hours, as the 7-day option recommends.
• If every depth is refused across several sessions, ask your broker whether your login may download tick history, quoting rp_code 13.

What it is not

• Not a change to your candles: the rebuild writes bubbles only.
• Not available on bridges or crypto: the button appears on charts that provide a Rithmic contract.

When to contact support

If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Include the depth chosen, the contract and the exact message.