“History loading stalled”: the Senzoukria chart gauge stops moving

If a history download sends no progress for 120 seconds, Senzoukria stops waiting, closes the loading gauge on what the cache and the live feed already have, and says “History loading stalled”. Reload history restarts the download.

Senzoukria · Troubleshooting · Updated September 2026


At a glance

Notice
“History loading stalled — the chart keeps running on cached and live data.”
Watchdog
120 seconds without any progress event
Manual retry
⚙ → Trading Settings → Reload history
Replay equivalent
“The backend stopped responding while loading (no progress for 90s).”

What you see

The loading overlay stops at a percentage, then disappears and the chart shows “History loading stalled — the chart keeps running on cached and live data. Retry from the chart settings (⚙ → Trading Settings → Reload history).”

Why it happens

A healthy download emits a progress event every few seconds, one per chunk, and skips empty windows quickly. Two minutes without a single event means the download is dead, not slow. That happens when the channel between the interface and the backend breaks mid-download: a webview reload, a refused IPC socket, or a backend that stopped. Without the watchdog, the overlay would stay frozen on its last percentage forever; with it, you get a usable chart and an honest notice.

How to fix it

  • Open ⚙ → Trading Settings → Reload history to start a new download.
  • If it stalls again at the same place, restart the app and open the chart again.
  • Reduce the history range in Trading Settings if you asked for a long window on a busy contract; a week of 1-minute footprint is many ticks.
  • Check the connection badge: a broker connection that drops during the download also ends it.

What it is not

  • Not a refused request: refusals have their own notices with codes.
  • Not a slow broker: a slow download still emits progress and does not trigger the watchdog.

When to contact support

If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Mention the percentage where it stopped, the history range, and whether it happens after the app was left in the background.

In the same section

This page in other languages

Frequently asked questions

Is anything lost when the watchdog fires?
No. The gauge closes on what the cache and the live feed already have, and the notice tells you how to retry.
Why 120 seconds?
Because a working download reports progress every few seconds. Two minutes of total silence is treated as a dead download.

Keep reading