Does Retry fire automatically?

No. Nothing restarts on its own; the Retry is always a manual action.

The notice stayed after I changed pair. Is that normal?

No. Each heatmap error belongs to one instrument and one subscription, so a new pair starts with an empty notice slot; if an old notice remains, click Hide this notice and report it.

“No market depth received” on a crypto heatmap in Senzoukria

On Binance and Bybit pairs, Senzoukria raises “No market depth received” when the order book subscription was accepted but no book arrived within 15 seconds. The notice is a local diagnosis, not an exchange refusal, and offers a Retry that subscribes again.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Title: “No market depth received”
Body: “No order book received for {symbol} after {seconds} s. The subscription was accepted, but the depth feed has sent nothing.”
Delay: 15 seconds, crypto only
Action: Retry (replays the whole subscription)

What you see

A notice over the heatmap titled “No market depth received” with “No order book received for {symbol} after {seconds} s. The subscription was accepted, but the depth feed has sent nothing.” It has a Retry button and “Hide this notice”.

Why it happens

A crypto market quotes continuously and Binance usually delivers its snapshot within one to two seconds, so 15 seconds of silence after an accepted subscription is abnormal. The case that motivated the alert: Binance reset the order book socket, the task ended, and the view would otherwise have waited forever. The notice is written by the heatmap itself, in the interface language, and is never presented as the exchange’s wording. If the backend already reports the book state (for example a reconnection in progress), the notice is not raised, to avoid a Retry in the middle of bounded reconnection attempts.

How to fix it

Click Retry: it replays the subscription from scratch.
Switch to another pair and back, or reopen the heatmap.
Check your internet connection and any firewall that could block the exchange’s WebSocket.
If it happens on one market only (Spot or Perp), try the other one to see whether the problem is on the exchange side.

What it is not

Not a refusal from Binance or Bybit: no exchange message was received.
Not a missing API key: the crypto feeds are public and need no account.
Not shown on Rithmic, where a closed market legitimately sends no book.

When to contact support

Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Include the pair, the market (Spot, Perp or Bybit) and how many Retries you tried.

In the same section

This page in other languages

Frequently asked questions

Does Retry fire automatically?: No. Nothing restarts on its own; the Retry is always a manual action.
The notice stayed after I changed pair. Is that normal?: No. Each heatmap error belongs to one instrument and one subscription, so a new pair starts with an empty notice slot; if an old notice remains, click Hide this notice and report it.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.