Tradovate 2-Session Limit & DeviceQuotaReached
Desktop app, phone, and a TradingView tab all connected at once trips Tradovate's DeviceQuotaReached error. Here's the two-session limit, why it fires, and how to get back to one clean connection.
Nothing rattles you faster than Tradovate dropping the connection and freezing the chart while you're working a live position on ES or NQ. Run the desktop app, glance at the mobile app, and keep a TradingView tab open all at once, and sooner or later you'll trip the platform's DeviceQuotaReached error. That message is Tradovate telling you the account's session (device) quota has been exceeded, so it starts kicking connections offline.
The same root problem wears different masks: repeated 24-hour logouts, a “connection closed” banner, a chart that quietly stops updating, or getting booted out of a trade “for no reason.” The cause is almost always the same one, too many simultaneous logins on a single account. Here's exactly what Tradovate's two-session limit is, why DeviceQuotaReached fires, and how to get back to one clean, stable connection, the same discipline an automation bridge like PickMyTrade uses so your strategy never double-logs your account.
Quick Checklist for DeviceQuotaReached & Session Limits
- Signed in on more than one device? Log out of Tradovate everywhere except the one device you're actively trading from.
- Multiple TradingView tabs open? Close all but one. In TradingView, each browser tab counts as its own session.
- Desktop, web, and mobile all connected? Pick a single surface and sign out of the rest.
- Just saw DeviceQuotaReached? Fully log out of every session, wait a moment, then sign back in on one device only.
- Chart frozen or prices static? Sync your computer's clock and check your connection before you blame the platform.
- Reconnecting over and over? Stop. Rapid re-logins burn your API quota and can trigger a separate “Too Many Requests” lockout.
What "DeviceQuotaReached" Means
Tradovate limits each account to a small number of concurrent sessions, commonly described as two active sessions across all of its surfaces: the desktop app, the web trader, the mobile app, and any TradingView or third-party connection. Under the hood the limit is even tighter for live data. Tradovate permits only a single established market-data connection per user account, so opening a new session terminates the previous one. Log into Tradovate Trader and it ends your API or WebSocket session, and vice versa.
When your simultaneous logins push past what the account allows, Tradovate refuses the surplus connection and returns DeviceQuotaReached, literally, the device quota for this account has been reached. The server drops the extra connection with an abnormal close, which is why your chart freezes, your DOM stops printing, or you get bounced out of a position with no obvious explanation. It isn't a flaw in your strategy, and it isn't always a Tradovate outage. Most of the time it's the account defending its session cap against you being logged in three or four places at once.
TradingView makes this easy to trigger without realizing it. Every open TradingView tab connected to your broker holds its own session, so two tabs plus the desktop app is already more than the account wants to allow. Add the mobile app checking in and you're comfortably over the line.
Top Causes of DeviceQuotaReached in 2026
1. Logged in on multiple devices at once
The classic trigger: the desktop app on your trading PC, the web trader on a laptop, and the mobile app on your phone, all connected to the same account. Each one is a live session, and together they blow past the cap.
2. Several TradingView tabs open at the same time
In TradingView, each browser tab linked to Tradovate counts as a separate session. Two or three chart tabs open “just to watch” quietly consume your entire session budget before you place a single order.
3. Desktop, web, and TradingView all connected simultaneously
Mixing surfaces is the most common real-world version of this problem. You route orders from the Tradovate desktop app while a TradingView tab is still connected for charting. Both hold sessions, and the market-data connection can only belong to one of them at a time.
4. Rapid reconnect loops after a drop
When a session gets bounced, hammering the login button to get back in makes it worse. Frequent reconnections and repeated login attempts eat into Tradovate's hourly API request allowance and can escalate into a separate “Too Many Requests” (HTTP 429) cooldown on top of the session conflict.
5. A stale session that never closed
A browser crash, a laptop going to sleep and waking, or the platform's routine ~24-hour logout can leave a “ghost” session registered against your account. You think you're logged in once, but the server still counts an old connection, so a fresh login tips you over the quota.
How to Fix DeviceQuotaReached: Step by Step
Fixing Causes 1 & 2: Log Out of Every Session First
Leave your primary device connected
On your primary trading device, leave Tradovate open. This is the one session you'll keep.
Log out fully on every other device
On every other device (laptop, second desktop, phone), open Tradovate and log out fully rather than just closing the window. Closing a tab doesn't always end the session cleanly.
Close extra TradingView tabs
In your browser, close all but one TradingView tab connected to Tradovate. Extra tabs each hold a session even when you're not looking at them.
Confirm you're down to one session
Give it a few seconds so the server registers the dropped connections, then confirm you're down to a single active session.
Fixing Cause 3: Reconnect TradingView on a Single Tab
Check the broker connection
In your one remaining TradingView tab, open the broker Trading Panel and check whether it still shows a live Tradovate connection.
Disconnect and reconnect once
If it's stuck or showing an error, disconnect the Tradovate broker connection, then reconnect it once from that single tab.
Pick one order surface
Don't route the same account from both the Tradovate desktop app and a TradingView tab at once. Decide which one is your order surface for the session and keep the other for charting only.
Fixing Causes 4 & 5: Sync Your Clock, Wait Out Reconnects, Sign In Once
Stop the reconnect spam
If you just tripped DeviceQuotaReached or a 429, wait instead of retrying in a loop. Rapid attempts extend the lockout instead of clearing it.
Sync your system clock
On Windows, open date and time settings, turn on Set time automatically, and click Sync now. A clock even slightly out of sync causes frozen charts and failed connections that look exactly like session errors.
Clear stale sessions
If you suspect a ghost session after a crash or sleep/wake, fully close the browser or restart the desktop app so no orphaned connection stays registered.
Sign back in on one device only
With everything else logged out, log in fresh on your single chosen surface. You should reconnect cleanly and stay connected.
Contact support if it persists
If DeviceQuotaReached persists even though you're genuinely on one device, contact Tradovate support and ask them to clear any lingering sessions on the account.
Troubleshooting Table
| Error / Symptom | What it means | Fix |
|---|---|---|
| DeviceQuotaReached | The account's concurrent-session (device) quota was exceeded | Log out of every device and extra TradingView tab, then sign in on one device only |
| Logged out roughly every 24 hours | Tradovate's routine session refresh, worsened by having extra sessions open | Keep to a single session; simply log back in on that one device |
| "Too Many Requests" / HTTP 429 after reconnecting | Rapid re-logins consumed your hourly API request allowance | Stop retrying, wait out the cooldown, then log in once |
| Chart frozen or prices static | Session conflict, clock out of sync, weak connection, or an expired contract month | Sync the clock, use a stable connection, confirm the front-month contract, and drop to one session |
| Bounced out of a trade "for no reason" from TradingView | A second session took the single market-data connection away from the first | Consolidate to one connected surface for that account |
| Still disconnecting on a single device | A stale "ghost" session may still be registered on the account | Restart the app/browser; if it persists, ask Tradovate support to clear old sessions |
Prevent This with PickMyTrade
DeviceQuotaReached happens because a human ends up logged in from several places at once. Automating your execution removes most of that surface area. Your strategy fires from one disciplined connection instead of you juggling the desktop app, a phone, and three TradingView tabs:
- Single, disciplined connection, PickMyTrade routes your TradingView alerts to Tradovate through one managed link, so you're not stacking manual sessions that trip the device quota.
- Rate-limit-safe routing, order flow is spaced out to stay within Tradovate's request limits, avoiding the retry storms that escalate into 429 “Too Many Requests” lockouts.
- Entitlement & risk awareness, routing respects your account's limits and data-agreement state, so orders leave clean instead of bouncing.
- Multi-account sync, mirror one strategy across several accounts from a single bridge rather than opening a separate live login for each.
Automation doesn't raise Tradovate's session cap, but it means you rarely need more than one connection open, which is exactly what keeps DeviceQuotaReached from firing in the first place.
Trade From One Clean Connection
Start your free 5-day trial, route your TradingView alerts through one clean connection and trade disconnect-free.
Start Your Free 5-Day TrialFrequently Asked Questions
It means your account has more simultaneous sessions open than it's allowed, so Tradovate refused the extra connection. The device quota is the number of concurrent logins permitted across the desktop app, web trader, mobile, and TradingView.
Only a small number, commonly described as two active sessions across all of Tradovate's surfaces, with just one live market-data connection per account. In practice, treat it as one device at a time to stay clear of trouble.
Because both hold a session and the single market-data connection can only belong to one at a time. Opening a connected TradingView tab can pull that connection away from the desktop app, which then freezes or drops.
Yes. Every TradingView browser tab connected to Tradovate is its own session, so a couple of extra watch tabs can eat your entire session budget before you place an order.
The roughly 24-hour logout is Tradovate's routine session refresh, not a bug. It becomes disruptive when you also have extra sessions open, so consolidating to one login and simply signing back in usually settles it.
Hammering the login button to reconnect burns through Tradovate's hourly API request allowance, which triggers a separate HTTP 429 cooldown on top of the session conflict. Stop retrying and wait it out.
Frozen charts on a single session usually point to a clock that's out of sync, an unstable connection, or an expired contract month. Sync your system clock, move to a stable connection, and confirm you're on the current front-month contract.
A stale session can stay registered after a crash or sleep/wake. Restart the browser or desktop app to drop any orphaned connection, and if it still persists, contact Tradovate support to clear lingering sessions on the account.
This guide is for educational and informational purposes only and is not financial, investment, or trading advice. Trading futures and other leveraged products carries a substantial risk of loss and is not suitable for every investor. PickMyTrade is an independent third-party automation platform and is not affiliated with, endorsed by, or sponsored by Tradovate, Inc. "Tradovate" and all related names, logos, and trademarks are the property of their respective owners. Platform features and steps change over time, so always confirm the current process in the official Tradovate platform and documentation before acting.