A daily loss limit in trading is a predefined loss threshold that triggers a stated action, such as blocking new entries or requesting position closures. A complete rule defines the account or strategy covered, loss calculation, reset time and restart condition. An equity-based limit includes floating losses; a balance-based limit does not. Reaching a threshold and completing an exit are separate events, so the final loss can exceed the trigger amount.
Daily and weekly limits add a time boundary to the risk management framework. They address cumulative exposure from repeated or correlated losses. They do not establish a profitable strategy or replace position-level protection.
Daily loss limits at a glance
Scroll horizontally to read every column.
| Rule component | What must be specified |
|---|---|
| Scope | One strategy, one EA, one account or several accounts |
| Measurement | Net realised loss, equity loss including floating P&L, or another explicit definition |
| Threshold | Cash, percentage of a named baseline, or a defined R measure |
| Time boundary | Start, reset, timezone and daylight-saving treatment |
| Action | Block entries, cancel pending entries, request exits, halt processing, or a stated combination |
| Restart | Automatic reset at the next boundary or an explicit review and resume |
MetaTrader 5 distinguishes balance, which excludes open-position results, from equity, which includes floating profit or loss and other account adjustments.[1] A daily loss number without its measurement basis is incomplete.
How do you define and calculate a max daily loss?
The following is a start-of-day equity-floor convention, not a universal broker or prop-firm rule. Assume no deposits, withdrawals, credits or other external cash adjustments during the day. Let B₀ be the balance recorded at the chosen daily boundary, E be current equity and L be the chosen cash limit.
Daily equity loss = max(0, B₀ − E)
Equity floor = B₀ − L · Trigger when E ≤ equity floor
For a percentage limit p: L = B₀ × p ÷ 100
PineConnector's documented daily-protection examples also derive trigger equity from the day's starting balance.[3] The inclusive comparison above belongs to this illustrative rule; verify a particular implementation's exact boundary behavior.
For a balance-only version, substitute current balance for E. The rule then responds to booked results while leaving floating losses outside the calculation. Net daily loss allows booked gains to offset losses; a rule that sums only losing trades measures gross losses instead. Define costs and cash adjustments explicitly.
A limit stated in R also needs a denominator. A fixed daily reference of USD 50 makes a USD 200 limit equal to 4R. Summing trade-specific R-multiples when each trade has a different initial risk is a different measurement. The position sizing guide explains where the cash risk originates.
Worked example: balance, equity and remaining exposure
Illustrative numbers, not a recommendation or trading results. A hypothetical account starts the day with USD 10,000 balance and no open positions. A chosen 2% limit gives L = 10,000 × 2 ÷ 100 = USD 200 and an equity floor of USD 9,800.
| Observation | Value | Meaning under this rule |
|---|---|---|
| Booked net loss | USD 100 | Balance becomes USD 9,900 |
| Floating loss | USD 50 | Equity becomes 9,900 − 50 = USD 9,850 |
| Daily equity loss | 10,000 − 9,850 = USD 150 | USD 50 remains before the trigger |
| Additional loss from current quotes to existing stops | USD 80 | Equity at those stops would be USD 9,770, before further costs or slippage |
The stop scenario implies USD 230 daily loss, which exceeds the USD 200 threshold by USD 30. The threshold has not triggered at USD 9,850, yet existing exposure can already carry the account beyond it. Halting new entries alone does not remove that exposure.
The USD 80 is additional loss from current quotes, not the positions' original entry-to-stop risk. Adding original risk to an equity loss that already includes floating losses can double-count part of the exposure. This distinction matters when comparing a daily limit with portfolio heat.
What should a trading circuit breaker do when it triggers?
A trading circuit breaker is a condition paired with an action and a reset rule. For an account-level loss control, three actions have different consequences:
- Block new entries: leaves current positions exposed and may leave pending entry orders able to trigger.
- Request exits and cancel pending entries: attempts to remove exposure, but requires confirmation of closures and cancellations.
- Halt incoming signal processing: changes what the receiving system processes. It is not automatically an entry-only block.
Define which exit and management paths remain available during a halt. MetaQuotes documents ordinary broker-side SL/TP as stored and executed on the broker's server. MT5's terminal trailing stop instead runs in the platform.[1] A strategy-only exit requires its own signal and execution path.
A weekly limit follows the same design with a weekly baseline and boundary. A daily reset does not reset a separately defined weekly total. If both rules exist, specify which one keeps entries blocked when the daily rule resets but the weekly rule remains triggered.
What does strategy.risk.max_intraday_loss do in Pine Script?
As of 25 September 2026, TradingView documents strategy.risk.max_intraday_loss() as a strategy risk command. When its loss threshold is reached, it cancels pending simulated orders, closes the simulated open position and stops trading activity until the current session ends.[2]
On chart timeframes above one day, the documented limit applies per chart bar. A weekly chart therefore does not make the function a daily account control. The built-in session rule is also not automatically the custom start-of-day convention illustrated above.
The function operates on TradingView's simulated strategy. It does not read the receiving MT5 account's balance or equity. Another strategy, a manual trade or a broker-side stop can change that account independently. PineConnector's converter documents that it does not resynchronise simulated and broker positions.[6]
For an external workflow, trace each stage: the loss condition becomes true; an alert triggers; the webhook is delivered; PineConnector processes the message; the EA submits a request; the broker accepts it; a deal changes the position. A simulated closure is not evidence of the final broker position.
Which PineConnector controls can enforce a loss rule?
As of 25 September 2026, the EA account-protection guide documents Daily Loss and separate actions for reaching daily limits.[3] Those controls are more directly related to a loss threshold than a time filter.
Daily Loss: the number and the action are separate settings
The documented Daily Loss input uses 0 to disable it. Values greater than 0 through 1 are proportions of starting balance; values greater than 1 are cash amounts. On the guide's USD 10,000 example, 0.01 and 100 each represent a USD 100 threshold.
Do not copy percentages between fields. Daily Loss 0.01 means 1%, while an explicit message's vol_pct_bal_loss=1 means 1% for a new position.[4] The first is daily protection; the second is position sizing.
| Daily action | Documented consequence |
|---|---|
| Halt EA | Stops the EA for the day, then resumes at the next daily boundary |
| Close All Positions | Requests position closures and pending-order removal within scope; the EA continues operating |
| Close All Positions and Halt EA | Requests closures and halts the EA for the day |
The guide also documents a Daily Timezone offset but preserves conflicting reset descriptions. Confirm the actual boundary and calculated threshold in the Experts log for the installed EA, particularly with a non-zero timezone offset. Verify position scope when manual trades or other EAs share the account.[3]
accfilter: an account threshold, not a daily-loss counter
accfilter= passes a threshold interpreted by the receiving EA's Account Filter setting: balance, equity, free margin or margin percentage.[4] The number alone does not identify the metric, daily baseline or reset. The documented references leave equality behavior unresolved; do not present an exact-boundary pass/fail result without a demo check.
PineConnector's converter applies its entry filters to generated entry requests, not generated close requests.[6] That documented converter distinction does not establish that every other filter or halt mode exempts exit messages.
Trading Time Limit: a schedule rather than a loss measurement
The Portal Trading Time Limit processes signals inside a configured time window and halts them outside it.[5] It does not calculate daily losses or request scheduled closures. Its displayed local timezone differs from the separate EA active-hours settings, which use broker-server time.
eaoff: halting does not request closure
The syntax reference documents eaoff as halting incoming signal processing and eaon as resuming it. The separate closealleaoff command requests closures and cancellations within scope, then a halt.[4]
Illustrative control message, not a loss-monitoring implementation. In a TradingView alert's Message field, with your License ID replacing LicenseID:
LicenseID,eaoff,eaoffThe third field is the command word, as required by the syntax. This message requests a halt, not a close. A License ID may address several accounts. Automatic loss detection, an exit exemption and replay of signals received during the halt are not established by this message; those paths are not documented here, so test on demo.
What commonly breaks a daily-loss rule?
- Wrong baseline: start-of-day balance, start-of-day equity and a moving intraday peak give different thresholds.
- Wrong clock: the chart session, Portal schedule, EA daily boundary and broker-server day need not coincide.
- Incomplete scope: one strategy's simulated P&L does not include every trade in the account.
- Exposure after the trigger: pending orders, failed closes and price gaps can leave losses increasing.
- Assumed restart: reset, reattachment and manual resumption can change tracked state. Read the calculated baseline and active/halted state again.[3]
A demo acceptance check should exercise just below, exactly at and just beyond the threshold. Include floating losses, a pending order, a failed close and the next reset boundary. Record both remaining exposure and whether new entries are accepted.
For a prop-firm account, compare the current written rule's baseline, floating P&L treatment, costs and reset time with the implementation. A similarly named control is insufficient. The prop-firm drawdown types guide separates daily, static and trailing rules without assuming a firm's current allowance.
The pause and resume procedure covers the operational review. No universal daily-loss amount or percentage fits every account or strategy.
Frequently asked questions
What is a max daily loss in trading?
A max daily loss is a stated loss threshold for a defined trading day. The rule must identify whether it measures booked results or equity including floating losses, which account or strategy it covers, and what happens when it triggers. The threshold is not necessarily the final realised loss because existing exposure and execution can carry losses beyond it.
How do you stop trading after losses automatically?
An automatic loss control needs a measured loss, a threshold, a trigger action and a reset rule. Blocking new entries differs from closing positions or halting all incoming signals. TradingView can apply risk rules to its simulated strategy; an account-level implementation needs actual receiving-account data and confirmation of any broker closures.
Does a daily loss limit include open trades?
An equity-based daily loss limit includes floating profit or loss from open trades, subject to its stated calculation. A balance-only limit excludes open-position results until they are booked. Broker and prop-firm rules may use different baselines and cost treatments, so the name daily loss limit alone does not establish whether a particular open loss counts.
Does PineConnector eaoff close open positions?
PineConnector documents eaoff as halting incoming signal processing; it does not request position closure. The separate closealleaoff command requests position closures and pending-order cancellations within its applicable scope, then a halt. A closure request still needs broker confirmation. Check the receiving accounts, remaining positions and pending orders before treating exposure as removed.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account and no code was compiled.
Related reading
- Risk management: position, portfolio and account rules
- Position sizing methods and calculator
- Portfolio heat and correlated exposure
- Prop-firm drawdown types
- When to pause and resume automated trading
Sources
- MetaQuotes – Executing Trades: account state, stop orders and trailing stops, accessed 25 September 2026.
- TradingView – Strategies: risk management and the broker emulator, accessed 25 September 2026.
- PineConnector – EA settings: account protection, filters and active hours, accessed 25 September 2026.
- PineConnector – Syntax: account filter, volume units and EA controls, accessed 25 September 2026.
- PineConnector – Tasks: Trading Time Limit, accessed 25 September 2026.
- PineConnector – Pine Script converter: supported behavior and entry filters, accessed 25 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
