Daily Loss Limit on Tradovate: Setting One a Bot Respects

Most strategies carry a loss cap somewhere in the code. A variable, a counter, a condition that stops sending orders once the day is down enough. It feels like a limit. It isn’t one. A limit written into a strategy is a request. It is evaluated when the strategy evaluates, which on a five-minute chart means twelve times an hour, and it can only stop the next order. The position already open keeps losing money in between, and nothing in the script is watching. A daily loss limit on Tradovate lives somewhere else entirely: in the account, at the broker, checked continuously, with the power to flatten you mid-trade.

That difference is the whole article. Below is what Tradovate’s version actually counts and what it does the second it fires. Then how the prop firm sitting between you and the broker changes the rules. And how big the number has to be before a working strategy can survive under it.

Key Takeaways

• Tradovate’s Daily Loss Limit is labeled “Exits trades and locks trading”: it closes every position, cancels every working order, and locks the account until the next session.
• Tradovate measures it on net P&L including open positions, fees and commissions, continuously, over a trading day that runs 6:00 PM ET to 4:45 PM ET.
• We analyzed 13,633 MNQ five-minute bars over 51 sessions. The median bar hid $10 of adverse move behind its close, and the worst hid $306, per contract.
• Prop firm and evaluation accounts only expose the settings the firm allows, and evaluation accounts don’t get Trailing Max Drawdown at all.
• Sizing matters more than placement: on a 5-lot position, a $1,000 limit would have been touched from the session open on 72% of the sessions we measured.

Why doesn’t your bot respect the limit inside the strategy?

Because the strategy is blind between evaluations. A bot-side cap is checked when a bar closes or an alert fires. The loss it sees is the loss as of that instant, and an open position keeps moving in the gap. Across the 13,633 MNQ five-minute bars we analyzed, the median bar concealed $10 of adverse travel behind its own close, per contract.

That number sounds harmless until you look at the tail. We measured the part of each bar’s move against a long position that never shows up in the closing price. The distribution runs long. It reaches $30.50 at the 90th percentile, $74.44 at the 99th, and $306.00 on the single worst bar in the sample. Multiply by position size and the harmless number stops being harmless.

The sample is every 5-minute MNQ bar Yahoo Finance served for the 60 sessions ending September 23, 2026, deduplicated and filtered for null rows. Values use the micro contract’s $2.00 per index point. It measures the market, not any particular strategy. That is the point: this is the exposure a close-only check cannot see, whatever the strategy does with it.

There is a second failure that has nothing to do with timing. A strategy-side limit lives inside one strategy. Run two scripts on the same account, or the same script on two symbols, and neither one knows what the other has lost. The account is down; no individual script is. Each keeps trading, politely, inside its own budget.

A daily loss limit is a rule that stops trading once losses for a defined session reach a set amount. Where it is enforced decides whether it is a rule or a suggestion. Enforced in the script, it is a suggestion that a disconnect, a missed alert, a duplicate order or a second strategy can quietly overrule.

Ask the practical question instead of the philosophical one. If your VPS lost power right now, mid-position, would anything still be counting your losses? If the answer is no, you don’t have a daily loss limit. You have a preference.

What does a daily loss limit on Tradovate actually measure?

Net P&L, open and realized together, including fees and commissions, recalculated continuously. Tradovate’s Risk Settings documentation, refreshed on September 4, 2026, states the calculation plainly. Profit and loss limits are based on net P&L covering both closed trades and whatever is still open, measured in real time. The trading day runs from 6:00 PM ET to 4:45 PM ET the following afternoon.

Which two words in that sentence do the most work? “Open and realized” and “continuously,” and both change how a bot has to be built. “Open and realized” means an unrealized loss counts the moment it exists, on a position you are still holding. So the limit can fire on a trade that has not closed. “Continuously” means there is no evaluation cadence to slip through. The weekly counterpart runs Sunday 6:00 PM ET to Friday 4:45 PM ET on the same basis.

The three action labels

The Risk Settings panel groups everything into four tabs, and each setting carries a label describing what it does when it trips. That label is the part worth reading twice, because three of them behave very differently.

“Alert only” is the trap. Max loss per trade sounds like the tightest control on the panel. It is the weakest one there. It notifies you and takes no action, which for an unattended bot at 3:00 AM is indistinguishable from nothing. If you want something closed, you need a setting whose label says it closes things.

Where the documentation contradicts itself

There is also a contradiction sitting inside that same September 2026 article, and it matters for anyone running automation on a funded account. The live-account section defines the limits as net P&L including open positions. The table further down covers prop firm and evaluation accounts. It defines Daily Loss Limit as “the maximum realized loss allowed in a single trading day,” and Weekly Loss Limit as maximum total realized loss. Realized and net are not the same number while a position is open, and the documentation gives both answers on one page. We found no reconciliation anywhere else in the help center.

The practical response is not to guess. Open a Tradovate demo, put on a single micro contract, let it run against you, and watch whether the limit counter moves before you close the trade. That takes about ten minutes and settles the question for your specific account type, which is the only answer that matters. If you don’t have a sandbox set up for this kind of check, the Tradovate demo test plan walks through building one.

One more calculation note that catches people out: commissions are inside the number. A scalping strategy turning over forty round trips a day is spending real money on fees. Every dollar of it counts against the daily loss limit on Tradovate before a single tick of adverse price movement does.

What happens in the seconds after the limit trips?

Everything closes at once. When a Daily Loss Limit is reached, Tradovate closes all open positions and cancels all working orders. New positions are blocked until the next session opens at 6:00 PM ET. The account moves into liquidation-only status, and order tickets from every connected platform start bouncing. Liquidation-only is an account state in which the broker accepts orders that reduce or close an existing position and rejects orders that open a new one. It is not a suspension and not a violation. It is the account refusing to add risk, which is exactly what you asked it to do when you set the number.

For a bot, this is a good outcome expressed badly. Your webhooks keep firing, because TradingView has no idea anything happened, and each one returns a rejection. Nothing is broken; the account is doing its job. But if you have alerting wired to order failures, expect a burst of them. This one looks alarming the first time you read it. Tradovate’s own troubleshooting article lists the rejection you may see as an account set to liquidation only. Our Tradovate order rejection reference covers how it differs from a margin or symbol failure.

Why the exit overshoots the number

The uncomfortable part is that the exit is a market order. Tradovate says so in writing for Real-Time Trailing Max Drawdown. Because the close goes to market, fills are not guaranteed at the threshold level, and slippage in volatile conditions may realize a loss larger than the configured limit. A $1,000 limit is a trigger price, not a ceiling. Nobody advertises this, and it is the single most common reason a trader insists the limit “didn’t work” when it worked exactly as documented.

How much overshoot should you expect? Our bar data gives a rough shape. Of the 13,633 MNQ five-minute bars we measured, 39.6% moved at least $25 against a single long contract from the bar’s open. At $50 the share is 14.7%, at $100 it is 3.0%, and at $200 just 0.4%. A flatten that lands mid-bar in the wrong 3% of cases is not a malfunction; it is the cost of using market orders to enforce anything.

That is also why the answer is never “set it tighter to be safe,” since a tighter limit fires more often and every firing pays the slippage toll. The trailing drawdown explainer covers the same arithmetic for the drawdown side of the panel.

How do you set a daily loss limit on Tradovate?

Four clicks and a number, assuming your account type allows it. Log in, click Application Settings in the upper right, then open Risk Settings, which opens on Loss Protection, the first of its 4 tabs. Check the box beside Daily Loss Limit, the section expands, type a value, and click Save.

The panel refuses a value of zero. Tradovate’s documentation is explicit that no risk setting can be saved at $0. An invalid entry produces an inline error under the field, not a silent failure. That guard exists for a reason. Older guidance warned that saving a risk setting at zero would liquidate positions and cancel orders immediately, since the platform reads it as a limit already breached. If you are working from an older walkthrough, that is the one instruction not to follow.

A successful save confirms with “Account risk settings have been updated successfully.” You can change several settings before saving; the panel validates the whole batch at once.

Before you commit a number, work through the short list:

• Decide the enforcement layer first. If a setting’s label says “Alert only,” it will not stop an unattended strategy, so it belongs in your monitoring plan, not your risk plan.
• Set Daily Loss Limit and, separately, Max Open Positions. The first caps the damage; the second caps the sizing mistake that causes it.
• Leave Trailing Max Drawdown alone unless you understand that it does not reset daily and does not unlock on its own.
• Save, then reopen the panel and confirm the values are displayed. A panel that hangs on save is a known failure mode, and PickMyTrade documents the risk settings lockout symptoms it produces.

The tab most people skip

The Risk Settings Lock tab holds a single checkbox: lock risk settings if trading is locked. Turn it on and, once a limit closes your positions, your risk settings freeze along with your trading, so you cannot raise the limit and keep going. Settings unlock between 5:00 and 6:00 PM ET, in the hour before the next session opens.

Read the warning attached to it carefully, because it is unusual. Tradovate states that its representatives are not able to unlock those settings on your behalf. There is no appeal, no support ticket, no exception for a good reason. That is the feature. For anyone who has ever talked themselves into a wider limit at 2:00 PM, it is the most valuable checkbox on the page.

Why Trailing Max Drawdown is different

Trailing Max Drawdown deserves its own caution. It does not reset at the end of a trading day. Once the threshold ratchets upward it stays there for the life of the account, and an account locked by it does not unlock at the next session either. Getting it reopened means contacting support through Tradovate’s chat assistant. Older support material pointed traders at an email address for the same request, so expect the channel to have moved if you are following a 2024-era guide.

Why prop firm and evaluation accounts don’t follow the same rules

Because the firm, not you, decides which of the 9 settings on the panel exist for your account. Tradovate’s documentation states it directly. On a prop firm or evaluation account, any setting you don’t see is managed by your prop firm. Tradovate cannot override the configuration the firm has set. Trailing Max Drawdown is off the table completely, listed as unavailable on evaluation accounts.

This produces a split that trips up automated traders moving between account types. On a self-funded live account, the daily loss limit on Tradovate is yours to set, raise, lower or disable. On an evaluation or funded prop account, a firm-imposed loss rule runs underneath whatever the panel shows you. The panel may or may not let you set a tighter one on top.

The documentation across firms has not kept up. One large futures firm’s help center was last updated in March 2026. It still tells traders that risk settings “are not applicable to evaluation accounts and can only be used with live and demo Tradovate Brokerage accounts.” Tradovate’s own article, six months newer, devotes an entire section to configuring risk settings on prop firm and evaluation accounts and describes the exact menu path. Both pages were live when we checked on September 23, 2026. When broker documentation and firm documentation disagree, the broker is describing the platform and the firm is describing its own configuration of it. The only reliable test is opening the panel on your actual account.

Two practical consequences follow. First, never assume a limit carried over when you switched accounts, because risk settings are per account and a new evaluation starts empty. Second, your firm’s rule and your own rule are not the same rule, and yours should sit inside theirs by a comfortable margin, not at the same number. Our guide to prop firms running on Tradovate covers which firms use the platform and how their rule sets differ.

Editorial note: rule sets at funded futures firms change often, and the figures here describe the platform layer rather than any firm’s current terms. Check your own account’s Risk Settings panel and your firm’s published rules before sizing anything.

Where does PickMyTrade’s risk layer fit?

One level above the broker, doing a different job. PickMyTrade’s Risk Settings page holds 4 values per connected account: Daily Loss, Daily Profit, Weekly Loss and Weekly Profit. The docs say it restricts further trading once a value is reached. That is the soft layer: it stops new alerts from becoming new orders.

The distinction is worth stating precisely, because the two layers are often described as if they were the same feature. The broker-side limit is enforcement, and it reaches into open positions. The automation-side limit is admission control, and it governs what gets sent. You want both, set at different numbers, for the same reason a building has a door policy and a fire door.

Alongside the loss values, PickMyTrade’s Trading Time Settings define an active window with a start and stop time in Eastern Time. When the window closes, you choose what happens: leave positions open, close selected accounts, or close all accounts. For strategies that have no business holding through the settlement window, that end-of-window close is the control that matters more than any dollar figure. The multi-session automation guide covers how to run different windows on different accounts.

A worked example with three numbers

Suppose your firm’s rule is a $1,250 loss for the day. Set PickMyTrade’s Daily Loss at $800, so new entries stop while you are still well clear. Set Tradovate’s Daily Loss Limit at $1,050, so the account flattens itself well before the firm’s number. Leave the firm’s $1,250 as the line neither layer should reach. Three numbers, three different jobs, and the strategy never has to be the thing that stops.

Why bother with two numbers when one would do? Because of the failure case nobody plans for. If the automation service is unreachable, the alert never arrives and the soft limit is irrelevant, but the broker-side limit is still counting and still able to flatten. If instead the broker connection drops, the soft layer at least stops queuing new orders into a position you can no longer see. Neither layer covers both failures. Together they cover most of them. The full Tradovate automation guide shows how the routing between the two is wired.

How to size the number so the strategy can still work

Start from how far the market actually travels, not from a round number. We measured the maximum adverse excursion from the session open across 50 complete MNQ sessions, and the median session traveled $383 against a single long contract at its worst point. The 75th percentile reached $714 and the 90th reached $1,219.

Scale that by position size and the arithmetic turns brutal quickly. At three contracts the median session’s worst excursion is $1,148 and the 90th percentile is $3,656. At five contracts, $1,914 and $6,094. The worst session in the sample reached $1,557 per contract, which is $7,785 on a 5-lot.

Run the same data against common limit values and the sizing problem becomes obvious. A $1,000 daily loss limit would have tripped from the session open on 16% of sessions at one contract, 60% at three contracts, and 72% at five. A $500 limit reaches 36%, 78% and 84% across the same sizes. These are upper bounds, since they assume a position exposed to the session’s full adverse move with no stop. The ranking still holds. A limit that feels disciplined at one contract is a guarantee of daily lockouts at five.

Two rules fall out of this. Size the limit to the position, not to the account balance, since a fixed dollar limit means something completely different at one contract than at five. And check the ratio between your limit and your strategy’s own stop loss. If one stopped-out trade uses more than about a third of the daily limit, the limit fires on ordinary days rather than unusual ones.

For example, a strategy risking $250 per trade on a 2-lot MNQ position needs roughly $750 to $1,000 of daily room to take three normal losses without tripping. Set the limit at $500 and you have built a system that locks itself out on Tuesday. The automated risk management checklist works through the rest of the sizing questions, and the auto trail tick math covers the per-trade side.

Which lockout can a bot never trade through?

Trader Lockout, and it is the only control on the platform that a strategy has no path around. Trader Lockout is a manually enabled feature that locks a trader out across every account linked to their prop firm username, for up to 24 hours. Tradovate’s Client Services team cannot end it early on request.

Enabling it flattens all open positions across every simulation account tied to the username and cancels all working orders. The lockout rejects new orders on every platform and overrides existing Risk Settings while active. Duration options are 15 minutes, 30 minutes, one hour, end of session, or a custom time up to 24 hours. Tradovate rejects orders arriving from NinjaTrader Desktop or TradingView during the lockout, with a message naming the cause: “User-initiated trading lockout is currently active.” That last detail is what makes it useful for automation. The rejection happens at the broker. It does not matter whether your webhook fired, whether the automation service was running, or whether a second strategy you forgot about was still armed. There is no state anywhere in your stack that can produce a fill.

So why isn’t this the answer for everyone? The limitations are real, and they are worth knowing before you count on it. Trader Lockout runs only on simulation accounts at a prop firm partnered with NinjaTrader or Tradovate. It is explicitly unavailable on demo accounts, Sim101 accounts, live Tradovate Brokerage accounts, live funded prop firm accounts, and accounts at firms outside that partnership. It also ignores account groups: every account under the username locks, not only the group you were trading. And it can only be enabled from the Tradovate Web app, not from NinjaTrader Desktop or TradingView, though once active it applies everywhere.

So the honest summary is awkward. The strongest lockout on the platform covers exactly the account type where most automated prop traders spend their time. Not the funded account, where the stakes are highest. On a funded account, the Daily Loss Limit with the Risk Settings Lock enabled is the closest equivalent, and it is close enough.

Frequently Asked Questions

Where the limit belongs, and why it isn’t in your script

The number you can trust is the one your strategy cannot reach. A cap inside a script stops the next order. An account-level daily loss limit on Tradovate closes what is already open, cancels what is still working, and never asks. Everything else in this article is detail hanging off that one distinction. So the setup is layered, not singular. Put the hard stop in Tradovate’s Risk Settings and check the Risk Settings Lock. Put a lower soft stop in your automation layer so new entries dry up before the hard stop is anywhere near. Size both from how far the market moves at your position size, not from a round number that sounded disciplined. Then leave them alone, which is the part the lock is there to help with.

PickMyTrade routes TradingView alerts to Tradovate and to prop firm accounts with per-account risk values and time windows sitting in front of every order it sends. Start a free trial and wire the soft layer in, or read the Tradovate automation overview first if you are still mapping out the setup.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: Automate TradingView Indicators with Tradovate Using PickMyTrade