“A history load is already running for {symbol}” in Senzoukria

What you see

The chart shows “A history load is already running for {symbol}” followed by “A previous load of this instrument has not finished. Most often it is the same instrument open in a second window. The chart retries on its own and nothing is lost.” If the second attempt finds the place still taken, the text becomes “Another history load is still running for this instrument. The chart keeps running on cached and live data — retry from the chart settings (⚙ → Trading Settings → Reload history).”

The bubble rebuild in the Big Trades settings has its own version: “A history load is already running on this contract. Wait for it to finish, then try again.”

Why it happens

The gateway accepts one history session at a time, and the app guards each instrument so two loads do not fight. The most frequent source is the same contract open in two charts, a detached window, or a tile of My pages. The retry is bounded on purpose: one attempt after 3 seconds, never a loop, so the notice changes wording instead of promising a retry that will not come.

How to fix it

• Close the other charts, detached windows or page tiles showing the same contract.
• Wait a few seconds: the first retry is automatic.
• If the “still running” wording appears, open ⚙ → Trading Settings → Reload history. The modal closes so the progress paints on the chart.
• Avoid launching a bubble rebuild while the chart itself is downloading history.

What it is not

• Not a broker refusal: this guard is the app’s own.
• Not data loss: the chart keeps its cache and the live feed.

When to contact support

When none of this helps, write to support through Menu → Report a problem or on the Senzoukria Discord. Say how many windows showed the contract and whether the notice survived closing all of them and reloading history.