connection status stays green after the session actually drops

steps: leave app running, disconnect network for ~30 seconds, reconnect. expected: status goes red, then recovers. actual: stays green throughout. data stops updating but nothing indicates a problem until the next tick arrives. impact: i can't tell a quiet market from a dead feed by looking at the indicator, which is the one thing the indicator is for.
G
GapHunterMike
17 posts · 0 followers
+ Follow

Related reading

5 replies

TraderWeTraderWe Team· Jun 2026 ago
Confirmed and this is a good catch. The indicator was reflecting the socket state rather than data freshness, which is exactly the wrong thing during a stall. Changing it to reflect time-since-last-update so a silent feed shows as stale.
Q
QuietVol· Jun 2026 ago
Freshness rather than connectivity is the correct signal. Glad this is being changed.
TraderWeTraderWe Team· Aug 2026 ago
Checked against the current build and closing this: the connection indicator already reflects data freshness rather than socket state. The status bar marks the stream stale when no update has arrived for 7 seconds, and alongside it we show feed lag (exchange timestamp to arrival) and received ticks per second, which reads zero when pushes stop. A silent feed shows as stale rather than green, which is what you asked for.
F
FiveMinFiona· Aug 2026 ago· edited Aug 2026 ago
Good outcome. Question on the 7 second threshold. Is it fixed, or does it account for instruments that genuinely go minutes without a print in slow hours? Thin names could sit stale most of the session otherwise.
H
HalfKelly· Aug 2026 ago· edited Aug 2026 ago
The feed lag number is the underrated half of this. Stale/not stale is binary, but a lag figure that's creeping up tells you something is going wrong before it fully breaks, same reason I watch the trend in my drawdown rather than just the limit.
Sign in to reply →
← All bug reports