“The broker refused the subscription to {symbol}” in Senzoukria

This notice means the Rithmic login went through but the market data subscription for that contract came back refused. Senzoukria lists the possible causes by frequency, keeps the broker’s exact wording, and never presents one cause as certain.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Message
“The broker refused the subscription to {symbol}”
Measured
“the login went through, and the subscription came back refused”
Where
Banner on the footprint chart or the heatmap; “Data subscription” step of the connection diagnostic
Unrecognised refusals
Shown as “This refusal has not been seen here before”, message unchanged

What you see

A notice titled “The broker refused the subscription to {symbol}” with “Measured: the login went through, and the subscription came back refused. That is what is known.” Under “Possible causes, most frequent first” the app lists its hypotheses, then “None of these is established by what was measured.” The broker’s own text sits folded under “The broker’s exact wording”, with “Copy the exact message” and, when a code was returned, “Broker code {code}”.

A refusal that matches none of the known shapes is titled “This refusal has not been seen here before” and shows the message unchanged, without any interpretation.

Why it happens

  • Another window or platform uses the same login on this instrument.
  • The contract is no longer the front month: some systems refuse an expired symbol, others accept it and stay silent.
  • The exchange or symbol is spelled differently on this system; the notice shows the form the broker expects.
  • The market is closed for this contract, and some systems refuse rather than stay silent.
  • The login may not be provisioned for this data. The notice adds that a refusal does not establish it.

How to fix it

  • Open the current front-month contract from the symbol picker rather than an old symbol from your recent list.
  • Close other windows or platforms signed in with the same login, then click “Try again”.
  • Check the clock: outside CME trading hours, retry after the next open.
  • Run the connection diagnostic; it tests the subscription on the current front-month MNQ and tells you whether the problem is specific to one contract.
  • If it persists, ask your broker the question printed by the app: “is my login enabled for {exchange} data, under which system name, and how many simultaneous sessions may it open?”

What it is not

  • Not a login failure: the login was accepted.
  • Not proof of missing entitlements. Refusals worded identically have had different causes.

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. Paste the exact wording and the broker code; the code alone “names no cause” but it is useful to your broker.

In the same section

This page in other languages

Frequently asked questions

The notice shows a broker code. What does it mean?
The code is kept because your broker’s support will ask for it. On its own it names no cause, and the app does not translate it into one.
Will hiding the notice fix the empty chart?
No. “Hide this notice” only hides the text; the chart stays empty until the subscription succeeds.

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.