Concurrent login limit (one login, one session)
A concurrent login limit is a provider's rule on how many sessions one set of credentials may hold open at the same time. Many futures data and routing services allow a single live session per login and service, so opening a second platform on the same login either disconnects the first or is refused, which often looks like a data failure.
Senzoukria · Glossary · Updated September 2026
Definition
Data and routing providers license and meter usage per login. To enforce that, their gateways limit how many sessions a login can hold for a given service at once. When the limit is one, a second login attempt ends the first session or is rejected, depending on the provider.
How it shows up
- A chart that was live freezes the moment another platform opens on the same login.
- A login succeeds but no data arrives, because another session holds the market data entitlement.
- Two platforms fight: each reconnect pushes the other out.
- An automatic reconnection loop that keeps colliding with a session the user opened elsewhere.
Worked example
A trader runs the broker's own platform and a third-party charting application on the same login, with a limit of one market data session. Session count: 2 requested, 1 allowed, so one of them loses its data. Closing one platform, or buying a second login where the firm sells one, restores a one-to-one match.
In Senzoukria
The Rithmic documentation in the application states that Rithmic allows one concurrent market-data session per login: close R | Trader Pro or another platform first, or buy the firm's second-login add-on. The account feed mirrors one broker connection at a time because providers such as Apex or Rithmic allow a single concurrent order-plant session per login. When the connection diagnostic finds every step accepted but no tick arriving, another session open on the same login is one of the two causes it always keeps on the list. The watchdog for silent order and PnL sessions only logs instead of re-logging automatically, because some prop-firm systems refuse concurrent logins.
Common mistakes
- Leaving the broker's platform running in the background while connecting another application.
- Sharing one login across two computers.
- Reading a displaced session as a platform bug.
Related
In the same section
- Confidence interval
- Composite profile
- COT report
- Consistency rule
- Color
- Consolidated tape
- Colocation
- Contango
This page in other languages
Frequently asked questions
- Can I run two platforms on one Rithmic login?
- Only within the concurrency the provider and firm allow. With one market data session per login, the second platform takes over or is refused. Some firms sell an additional login for exactly this purpose.
- Why did my data stop when I opened my phone app?
- If the phone app uses the same login and service, it may have taken the only allowed session. Closing it, or using a separate login for it, lets the desktop session receive data again.