“Everything was accepted, no data is arriving”: Senzoukria connection diagnostic

When the connection diagnostic passes gateway, system, login and subscription but no tick arrives, Senzoukria says so instead of blaming an entitlement: a closed market, an expired contract, a second session on the login or an unprovisioned login all look the same on screen.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Message
“Everything was accepted, no data is arriving”
Step line
“No tick in {seconds} s.” under “First tick received”
First-tick wait
Between 10 and 30 seconds, derived from the gateway heartbeat
Where
Connection form, step 3 · Credentials → “Run the diagnostic”

What you see

The diagnostic lines turn green up to “Data subscription”, then “First tick received” fails with “No tick in {seconds} s.” and a block titled “Everything was accepted, no data is arriving”: “Measured: the gateway answered, it serves this system, the login was accepted and the subscription was accepted. No tick has arrived since.”

Why it happens

The app lists four causes, most frequent first, and states that none is established by what was measured:

  • The market is closed for the contract, or its session has not opened yet. A quiet feed and a broken feed look the same.
  • The symbol is no longer the front month: an expired contract still accepts a subscription and trades nothing.
  • Another session is open on the same login in another platform; some brokers allow one market-data session per login and leave the second silent.
  • The login may not be provisioned for the requested data, which only your broker can confirm.

How to fix it

  • Check the CME schedule: futures trade from Sunday 17:00 to Friday 16:00 Chicago time, with a daily break from 16:00 to 17:00 CT. Retry during trading hours.
  • Let the diagnostic use its own probe contract (the current front-month MNQ, computed from the date), and open the current contract on your chart.
  • Close other platforms signed in with the same login and run the diagnostic again.
  • If the market is open and the other checks pass, send your broker the sentence the app prints: “is my login enabled for third-party API access, for which data, and under which system name?”

What it is not

  • Not proof that the software is broken: every layer answered.
  • Not proof of missing entitlements: an accepted subscription followed by silence does not establish it.
  • Not shown when the cause is known: on a closed market, or when the server ejected the session (forced logout), this block does not appear, so a Sunday afternoon is never turned into an entitlement question.

When to contact support

Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Use “Copy the result”: the copy contains each step, its measured outcome and the wait, without your password.

In the same section

This page in other languages

Frequently asked questions

How long does the diagnostic wait for the first tick?
Between 10 and 30 seconds. The wait follows the heartbeat interval the gateway announces, and the result states the number of seconds actually waited.
It is Sunday afternoon in Europe. Is that why?
Possibly. The CME reopens on Sunday at 17:00 Chicago time; before that no tick is published, and the diagnostic is designed not to call that a failure.

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.