Why do lost events matter?

Each missing event breaks the life of an order, so the split between withdrawn and executed becomes partial. The panel says so rather than showing a clean but wrong figure.

Can the heatmap show adds and pulls without MBO?

The heatmap can infer adds and pulls from the aggregated book, labelled as inferred and never presented as an MBO observation.

Liquidity tracker unavailable: “this tracker needs the order-by-order feed”

The Liquidity tracker of the Senzoukria heatmap follows each order’s life to tell withdrawn liquidity from executed liquidity. It needs the order-by-order (MBO) feed, which only Rithmic provides, so its switch is disabled on other sources.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Disabled note: “Unavailable on {source}: this tracker needs the order-by-order feed, which only Rithmic provides.”
Empty state: “No order book activity yet. This panel needs the order-by-order feed (MBO)…”
Partial data: “{n} order events lost — the picture is partial.”
Where: Heatmap settings → Liquidity tracker

What you see

In the heatmap settings, the Liquidity tracker switch is greyed out with “Unavailable on {source}: this tracker needs the order-by-order feed, which only Rithmic provides.” On Rithmic, the panel may show “No order book activity yet. This panel needs the order-by-order feed (MBO): it reads each order’s life, not just the visible totals.” or warn “{n} order events lost — the picture is partial.”

Why it happens

Telling a cancelled order from an executed one requires seeing each order: aggregated depth only shows totals per price. In 0.46.0 the tracker is wired to Rithmic only; on the crypto feeds, Databento, dxFeed and the bridges the switch is disabled, because users who turned it on there saw nothing and nothing said why. On Rithmic, the MBO subscription can be refused intermittently, in which case the DOM’s MBO badge is grey and the tracker has nothing to read.

How to fix it

Use a Rithmic connection as the heatmap source.
Check the MBO badge in the DOM header: lit means the order-by-order book is active.
If the panel stays empty during market hours, reload the chart to resubscribe.
Read the result with its note in mind: “Withdrawn” includes normal market-maker requoting and does not mean deceptive behaviour.

What it is not

Not a bug on crypto: the data type does not exist on that source here.
Not a claim of spoofing: the tracker separates withdrawal from execution, nothing more.

When to contact support

If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. On Rithmic, include the state of the MBO badge and the number of lost events shown.

In the same section

This page in other languages

Frequently asked questions

Why do lost events matter?: Each missing event breaks the life of an order, so the split between withdrawn and executed becomes partial. The panel says so rather than showing a clean but wrong figure.
Can the heatmap show adds and pulls without MBO?: The heatmap can infer adds and pulls from the aggregated book, labelled as inferred and never presented as an MBO observation.

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.