Senzoukria · Troubleshooting

“Order book feed stopped” and BOOK STOPPED on the Senzoukria heatmap

When the backend cannot resynchronize a crypto order book after its bounded reconnection attempts, Senzoukria stops showing the last known book as live and says “Order book feed stopped”. Retry becomes available after a short delay and opens a new subscription.

Updated September 2026First published 25 September 2026

On this page
  1. At a glance
  2. What you see
  3. Why it happens
  4. How to fix it
  5. What it is not
  6. When to contact support
  7. Related pages
  8. In the same section
  9. This page in other languages
  10. Frequently asked questions

At a glance

Title
“Order book feed stopped”
Body
“The {symbol} order book could not be resynchronized after {attempts} attempts…”
Binance limit
12 failed sessions in a row, waits up to about 36 s between them
Retry
Offered after 15 s: “Retry in {seconds} s”, then “Try again”

What you see

The status line shows BOOK STOPPED, and a notice reads “Order book feed stopped — The {symbol} order book could not be resynchronized after {attempts} attempts. The last known book is no longer shown as live. Retry opens a new subscription.” The Retry button counts down (“Retry in {seconds} s”) before it becomes clickable. On the crypto footprint, the DOM Profile reports “DOM Profile · order book feed stopped — no live depth shown”.

Before that point, the status line may show BOOK SYNCING, BOOK RESYNC or BOOK RECONNECT n/m while the backend tries again.

Why it happens

A local order book is rebuilt from a snapshot plus a stream of changes. When the chain breaks, the backend closes the session and opens a new one after an increasing delay, never shorter than a delay the exchange imposes. On Binance, the twelfth failed session in a row stops the task: waits go up to 30 s plus 20% jitter, about 36 s. The heatmap then invalidates the book from the last proof of validity, so a gap is marked instead of a frozen book looking live.

The Retry waits 15 seconds because each Retry starts a fresh task with its own attempts; a burst of clicks would recreate the loop the limit exists to prevent. Nothing restarts automatically.

How to fix it

  • Wait for the countdown, then click Try again.
  • Check your network: repeated drops on every pair point to the connection, not to one market.
  • If only one pair fails, switch pair and back later; the exchange may be throttling that stream.

What it is not

  • Not a frozen market: the last book is deliberately no longer presented as live.
  • Not an account problem: crypto feeds are public.

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 pair, the attempts count shown, and whether the Technical detail line quoted a reason.

In the same section

This page in other languages

Frequently asked questions

Why can’t I click Retry right away?
Each Retry starts a new task with its own series of attempts. The 15-second delay stops a burst of clicks from hammering the exchange.
Is the heatmap history lost?
No. The period without a valid book is marked as a gap; the rest of the map stays.
NEXT

Keep reading