Feed status (connected badge)

Feed status is the indicator a platform shows for the state of its market-data connection: idle, connecting, connected, live, reconnecting or error. Connected means the session is open; live means data has actually arrived, and the two are not the same thing.

Senzoukria · Glossary · Updated September 2026


The states and what each one asserts

  • IDLE: no connection attempt in progress and no broker selected.
  • CONNECTING: the handshake with the gateway has started and has not completed.
  • CONNECTED: the login was accepted; nothing is yet said about data.
  • LIVE: ticks are arriving on the subscribed symbol.
  • RECONNECTING: the session dropped and a bounded retry is in progress; the gap is real and is not filled silently.
  • ERROR: the last attempt failed with a reported reason.

Connected is not live

A login can be accepted while the market is closed, while the symbol is an expired contract, or while the account lacks the data entitlement for that symbol. Each of those leaves the badge at connected with an empty chart. A quiet feed and a broken feed look the same on screen, which is why the transition to live is driven by a received tick, not by the handshake. On a bridge, the status also depends on the bridge indicator running in the host platform: a heartbeat every few seconds is what keeps the state honest.

In Senzoukria

The connection badge shows LIVE, CONNECTING, RECONNECTING, ERROR, IDLE, CONNECTED or No broker. On the Trading screen, the desk's Connection and Account stages show their real state: Feed connecting, live feed with the account id, Feed error or No account feed, and the preparation hint says to wait for the live badge before expecting positions. Settings can play a sound for Broker connected and Broker disconnected.

With no broker connected, the chart opens on history already downloaded to this machine, scrolls and computes as usual but does not advance; a notice makes that explicit, and Broker connected, the chart is live again appears when the feed resumes. On the Quantower bridge, live trades and depth updates follow the session history with a heartbeat every five seconds.

Common mistakes

  • Treating CONNECTED as confirmation that historical data will load; history is a separate capability.
  • Assuming a RECONNECTING episode replayed the missed trades; the gap remains unless a resubscription with replay is supported by the feed.
  • Reading an empty DOM as an empty book rather than as a feed that has not delivered depth yet.
  • Ignoring No broker and reading a static cached chart as the current market.

This page in other languages

Frequently asked questions

The badge says CONNECTED but nothing moves. Is the connection broken?
Not necessarily. The login is accepted; data may be absent because the contract is outside its session, the expiry has rolled, or the symbol is not entitled. Run the connection diagnostic: if every stage passes and no tick arrives, it lists the possible causes by frequency rather than declaring a fault.
What does the chart show when the feed is disconnected?
The history already stored on the machine. It scrolls, zooms and computes exactly as usual but does not advance. Live ticks, the order book, the DOM and the bar in progress need a connected broker, and the chart says so in a notice until the feed returns.
Does reconnecting fill the gap?
Reconnection restores the session; whether missed trades are recovered depends on the feed. The desktop does not invent the missing interval, so a gap after a reconnect is shown as a gap. Compare bar counts around the episode before relying on that stretch of data.

Keep reading