“DOM Profile · … — no live depth shown” on a Senzoukria crypto chart
On crypto footprints, the DOM Profile and the liquidity walls disappear during an order book gap, and a notice names the book state. After the backend gives up, the notice turns red with a timed Retry.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Gap notice
- “DOM Profile · {state} — no live depth shown”
- States
- BOOK SYNCING · BOOK RESYNC · BOOK RECONNECT n/m · BOOK STOPPED
- Stopped
- “DOM Profile · order book feed stopped — no live depth shown” with Try again
- Applies to
- Binance and Bybit charts with DOM Profile or liquidity walls on
What you see
In the notice stack above the crypto chart, an info line “DOM Profile · BOOK RESYNC — no live depth shown” (or another state), while the DOM Profile vanishes and the walls freeze. If the backend abandons, the line becomes red: “DOM Profile · order book feed stopped — no live depth shown”, with Try again once the delay has passed.
Why it happens
The DOM Profile reads the live order book. When the book chain breaks, the backend resynchronizes or reconnects with bounded attempts. During that time the depth is not valid, so the app removes it rather than show a book that may be wrong. Without the notice, users would read “indicator switched off” or “no liquidity”.
How to fix it
- Wait: BOOK SYNCING and BOOK RESYNC usually resolve within seconds.
- On BOOK STOPPED, wait for the Retry to become available and click Try again.
- Check your network if every pair shows the same state.
- Keep in mind that the footprint and trades continue during the gap.
What it is not
- Not a disabled DOM Profile: the setting is unchanged.
- Not shown on Databento CME charts, which handle their book differently.
When to contact support
If the steps above do not change anything, send the case from Menu → Report a problem, or ask on the Senzoukria Discord. Include the state shown, the pair and how long it lasted.
Related pages
In the same section
- Python engine unavailable
- Databento book refused
- Accepted but no data
- NinjaTrader bridge stuck connecting
- History could not be completed
- Anthropic refused this key
- History shorter than requested
- Alpaca unauthorized
This page in other languages
Frequently asked questions
- Does the footprint stop during a book gap?
- No. Trades and footprint bars continue; only the depth-based layers are hidden.
- Why does the Retry wait?
- Each Retry starts a new set of attempts; the delay prevents a click burst from restarting the loop the limit is meant to stop.