Tradovate 'Not Found: md/get chart' at Sign-In
The desktop app throws a red “Not Found: md/get chart” banner at sign-in, but the mobile app loads the same charts perfectly. That mismatch tells you exactly where the problem is, and it's almost always a stale cache.
You open the desktop app, log in, and instead of your charts you get a red Not Found: md/get chart banner. Then you grab your phone, open the mobile app, and everything loads perfectly. Frustrating, but that mismatch is actually the good news: it tells you exactly where the problem is. Your account, your data subscription, and the exchange feed are all fine, the fault is sitting on your desktop, in the app or the browser you're signing in with. The md/getChart request is how the platform pulls your chart data as it loads, and “Not Found” just means that request didn't come back cleanly this time. In almost every case it's a stale cache or a bad session, and it clears with a few minutes of housekeeping. Here's how to fix it and stop it from coming back.
Quick Checklist
- Confirm it's desktop-only, if the mobile app loads charts fine, your account and data feed are healthy, so focus on the desktop.
- Fully quit and relaunch the app, a clean restart clears the most common transient glitch.
- Clear cache and cookies, for the desktop app's stored data, or for the Tradovate site if you use a browser.
- Update to the current version, an outdated build is a frequent cause of chart requests failing.
- Disable extensions / test incognito, ad and script blockers can break the market-data request in a browser.
- Reinstall if it persists, a fresh install replaces a corrupted build and wipes its local storage in one step.
What “Not Found: md/get chart” Actually Means
md/getChart is a market-data request. “md” is short for market data, and getChart is the specific call the platform fires to fetch the bars for the chart you're opening. When you sign in, the app runs a burst of these requests to paint your workspace. If one of them comes back with Not Found instead of chart data, you get the error banner and an empty or missing chart.
The important thing is what this error is not. It's not a billing problem, it's not your login being wrong, and, when mobile works, it's not your market-data subscription. A subscription gap would starve every device of quotes, not throw a one-off “Not Found” on desktop while your phone streams live. So treat this as a local desktop hiccup: the request left your machine in a state the server couldn't answer, usually because the app was working from a stale or corrupted cache, an outdated build, or a session that got tangled.
Top Causes in 2026
1. A stale or corrupted cache
The desktop app and the browser both cache data to load your workspace faster. When that cached data gets out of date or corrupts, often after an app update, a forced quit, or a network drop mid-session, the chart request can point at something that's no longer valid and come back Not Found. This is the single most common cause, and it's why a cache clear fixes it so often.
2. An outdated app or browser version
Tradovate ships fixes and performance improvements regularly. If your desktop app or browser has fallen behind, the chart-loading request it sends may not line up with what the current servers expect. Keeping the app and browser on their latest versions is the baseline cure for a whole class of loading errors, this one included.
3. A browser extension getting in the way
If you run the platform in a browser rather than the desktop app, ad blockers, script blockers, and privacy extensions are prime suspects. They can silently block or rewrite the market-data request that loads charts, and the result surfaces as Not Found. The dedicated desktop app runs in its own self-contained environment with none of your browser extensions loaded, which is exactly why it's often more stable than the browser.
4. A leftover or conflicting session
Tradovate limits how many active sessions you can hold at once across web, desktop, mobile, and TradingView. If old sessions are still hanging around, or you're signed in on several places at once, the desktop sign-in can land in a half-connected state where some data requests never resolve. Signing out everywhere and back in on one device clears it.
How to Fix It: Step-by-Step
Restart the app cleanly
Don't just close the window, fully quit the process. On Windows, close the app, then open Task Manager (Ctrl+Shift+Esc), find any lingering Tradovate entry, and choose End task. On macOS, right-click the dock icon and choose Quit, or force-quit from the Apple menu. Relaunch and sign in. A clean restart clears the transient version of this glitch surprisingly often, so it's always the first move.
Clear cache and cookies
If the restart didn't do it, wipe the stale cache. How you do this depends on how you sign in: Browser: open your browser settings, clear cached images/files and cookies for the Tradovate site (or clear browsing data for “All time” if you want to be thorough), then reload the platform and log in again. Desktop app: the app stores its own cache. If there's a data or cache reset inside the app's settings, use it; otherwise reinstalling accomplishes the same thing by wiping local storage. Heads up: clearing cookies signs you out, so have your credentials ready. Your saved workspaces and chart templates live server-side against your account, so they reload once you log back in, you're only clearing the local junk, not your setup.
Update the app and browser
Make sure you're on the current version. For the desktop app, check for an update prompt on launch or download the latest build from the official site and install over the old one. For the browser, update it to the newest release. Running the latest version removes the “old build talking to new servers” mismatch that throws chart errors.
Disable extensions or test incognito (browser only)
If you're in a browser, open a private/incognito window and sign in there. Incognito runs with extensions off by default, so if the charts load cleanly, an extension is your culprit. Go back to your normal window and disable ad blockers, script blockers, and privacy extensions for the Tradovate site one at a time until you find the one causing trouble. If you'd rather skip the whole issue, switch to the dedicated desktop app, which doesn't load browser extensions at all.
Reinstall the desktop app
If it's still throwing the error, reinstall. This replaces a possibly corrupted or outdated build and wipes its local storage in one clean sweep, it's the most reliable fix when the lighter steps don't stick. Uninstall the Tradovate desktop app the normal way for your OS, download the current version from the official Tradovate download page, and install it fresh. While you're at it, if the problem started right after signing in on several devices, sign out of every session, web, desktop, mobile, and any TradingView connection, then sign back in on just this one machine to clear a session conflict.
Rule out a platform issue
If you've cleared cache, updated, reinstalled, and it still won't load, and especially if other people are hitting the same wall at the same time, check the official status page at status.tradovate.com. A wider outage or maintenance window is out of your hands and just needs waiting out. If the status page is green and the error only affects your desktop, it's still a local issue and reinstalling is your best lever.
Troubleshooting Table
| Situation | Likely Cause | Fix |
|---|---|---|
| Error on desktop, mobile works fine | Local cache or session glitch on desktop | Restart cleanly, clear cache/cookies, then reinstall if needed |
| Started after an app update or forced quit | Stale or corrupted cache | Clear cache and cookies, or reinstall to wipe local storage |
| Charts load in incognito but not normally | A browser extension blocking the request | Disable ad/script/privacy extensions for the site, or use the desktop app |
| App feels behind on features | Outdated build | Update the desktop app and browser to the latest version |
| Signed in on several devices at once | Session conflict / limit reached | Sign out everywhere, then sign in on one device |
| Everyone is affected at the same time | Platform outage or maintenance | Check status.tradovate.com and wait it out |
Keep Your Automation Running with PickMyTrade
A blank chart on the desktop is annoying on its own, but if you trade a strategy that fires from those charts, a sign-in glitch can mean missed entries and exits while you're busy reinstalling. PickMyTrade takes that dependency off your desktop:
- Server-side execution, your TradingView alerts route to Tradovate through PickMyTrade's infrastructure, so your trades don't wait on your desktop app painting charts correctly.
- Runs while you troubleshoot, clear your cache, update, and reinstall without your automation going dark, because the order flow doesn't live on your machine.
- Multi-account sync, mirror the same managed orders across accounts, so one glitchy desktop session doesn't leave positions unmanaged.
- Prop-firm-aware routing, respects your account's risk and data-agreement state so recovered orders don't get rejected.
Automate So a Chart Glitch Never Costs You a Trade
Your order flow runs server-side, so clearing cache, updating, and reinstalling never takes your automation offline.
Start Your Free 5-Day TrialFrequently Asked Questions
md/getChart is the market-data request the platform uses to pull chart data. “Not Found” means that request failed to return the chart it asked for as the app loaded. When it shows up only at sign-in on the desktop app while your phone works fine, it's almost always a local glitch in the app or browser, a stale cache or a bad session, not a problem with your account or data feed.
If mobile loads charts normally, your account, subscription, and the exchange feed are all fine. That splits the problem cleanly: the fault is on the desktop side, usually a corrupted cache, an outdated app version, a browser extension interfering, or a leftover session. The mobile app has its own storage, so it sidesteps whatever the desktop is choking on.
Clearing cache and cookies for the Tradovate site will sign you out, so have your login handy. Your saved workspaces and chart templates are stored server-side against your account, so they come back when you log in again. Clearing cache does not delete your account settings.
Rarely, when it's tied to this specific pattern. A missing data subscription usually shows delayed or blank quotes across every device, not a one-off “Not Found” on desktop only while mobile is fine. If your phone shows live charts, your subscription is working and you should treat this as a local desktop issue.
The desktop app is a self-contained build of the web platform, so the cleanest reset is to fully quit it (end the process if needed) and relaunch, or reinstall it to wipe its stored data. If you use the platform in a browser instead, clear cache and cookies for the Tradovate site in your browser settings, or reset from within the app's own settings if that option is present. Confirm the exact current wording in the app's settings menu, since labels change between versions.
Reinstalling is the reliable fix when a cache clear and restart don't work, because it replaces a possibly outdated or corrupted build and wipes its local storage in one move. Uninstall the app, download the current version from the official site, and install it fresh.
Yes, if you run the platform in a browser. Ad blockers, script blockers, and privacy extensions can block or mangle the market-data request that loads charts. Test in a private/incognito window (extensions are usually off there) or disable them for the Tradovate site. The dedicated desktop app avoids this entirely, since it doesn't run your browser extensions.
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. or Bookmap. 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 platform documentation before acting.