Core concept · Free
The daily loss limit is the only funded futures rule that enforces itself without any action on your part. When your intraday loss reaches the cap, the platform closes your positions and restricts new entries — the session is over. What most traders don't know going in: hitting the DLL typically ends the session, not the evaluation. The evaluation continues the next trading day. But the losses are real, the trailing drawdown floor has moved, and the psychological state you're in after a DLL breach is exactly where accounts compound instead of recover. Knowing what actually happens, why most breaches occur, and how to respond without making it worse is the difference between a bad day and a failed evaluation.
Companion to "The daily loss limit explained" — this page covers what happens after the breach, not the mechanics themselves.
Part 1 of 4 — What the platform does
The daily loss limit is not reviewed by a human and it is not enforced at the end of the day. It is a live intraday loss ceiling that the platform monitors tick by tick. When you cross it, the response is immediate and automatic.
When your cumulative intraday loss reaches the DLL amount, the platform closes any open positions without input from you. If you are in a trade that was moving in your direction when an adverse move pushed your total session loss through the DLL, that position is closed by the system — not by your stop order. The fill price is whatever the market price is at the moment of the breach. This is distinct from a stop-loss order you set yourself: there is no guarantee of price, and news-gap scenarios can cause the position to close below your stop and at the DLL threshold simultaneously.
After the DLL triggers, most funded futures platforms prevent any new position entries for the rest of that trading day. The exact definition of "trading day" varies by firm — some use the calendar day, others use the futures session boundary (which crosses midnight). The practical result is the same: the platform does not let you open a new trade to "trade back" or recover the loss. This restriction is one of the design features of the DLL as an account protection mechanism — it forces the session to end before compounding can begin. Platforms that do not technically restrict re-entry still apply the cumulative loss calculation, meaning any additional loss after a partial breach further reduces the account balance and floor.
A DLL breach ends the session — it does not automatically terminate the evaluation. In the typical funded futures evaluation model, the DLL is a per-session rule, not a per-evaluation rule. The evaluation continues the next trading day. Your trailing drawdown floor has moved by the amount of the loss, and your profit target is unchanged, but the evaluation itself is live. What the breach costs you is the day's loss and the corresponding floor tightening — not the evaluation account itself. This is an important distinction because the correct response to a DLL breach (stop, review, reset next session) is very different from the response to a trailing drawdown breach (which does end the evaluation). Confusing the two leads to either unnecessary panic or insufficient seriousness about the floor damage done.
Part 2 of 4 — Stage matters
A DLL breach in an evaluation account and a DLL breach in a funded payout account are the same mechanical event but carry different consequences. Knowing which stage you're in determines the right response.
During the evaluation phase, a DLL breach ends the trading session for that day. The evaluation account remains active for the next session. You still have the same profit target to reach, but your trailing drawdown floor has tightened by the day's loss amount. For example: if your trailing drawdown maximum was $3,000 and your DLL breach cost $500, your floor is now $500 closer to your current balance, leaving you $500 less drawdown cushion for the remainder of the evaluation. The breach did not end the evaluation, but it raised the difficulty level of the remaining sessions by removing floor cushion without adding to the profit target. Some firms track DLL breaches across an evaluation phase and may add review steps after repeated breaches — check your firm's specific terms.
A DLL breach in a funded payout account (after you've passed the evaluation and are trading toward a withdrawal) carries more variable consequences depending on the firm. Some firms treat a funded-account DLL breach the same as an evaluation breach — session ends, trading resumes next day. Others reset the payout period, require a buffer to rebuild before the next payout request, or in cases of severe breach (where the loss significantly reduces the account below the funded starting balance), may initiate an account review. Because firm policies on funded-account DLL breaches vary more than evaluation-stage policies, it is critical to read your firm's payout terms specifically — the section governing what constitutes an account reset or termination event — before you are in this situation. Check your funded-firm-specific terms; the Funded Firm Radar summarizes each firm's general structure to help you locate the right document.
The correct response to a DLL breach in an evaluation is: stop, log it, review it the next session, continue the evaluation with adjusted floor awareness. The correct response to a DLL breach in a funded account is: stop, read your firm's terms immediately, understand whether the next session is normal or whether a buffer/review requirement applies, and only then plan the next session. The error most traders make is applying evaluation-stage casualness to a funded-account breach ("it's just a bad day, I'll trade tomorrow") when the funded-account terms may actually require a cooling period or buffer rebuild before the next trade. Know which stage you're in and read the terms for that stage specifically before resuming.
Part 3 of 4 — Root causes
A DLL breach is rarely a random event. Tracing back through the session almost always reveals one of three root-cause patterns. Identifying which one triggered the breach is the first step in preventing the next one.
The most common DLL breach pattern: one trade loses the maximum acceptable per-trade amount, and rather than ending the session or waiting for the next valid setup, the trader re-enters immediately to "get it back." The second trade often loses as well — sometimes because the market is in a trend against the original direction, sometimes because the entry was taken from an emotional state with a wider stop or a rushed setup. By the second or third re-entry, the cumulative session loss crosses the DLL. The key marker of this pattern is that the DLL breach did not happen on the first trade — it happened on the second or third after the first loss. If your pre-session plan includes a single-loss session stop (end the session if one trade reaches your maximum per-trade risk), this entire pattern is preventable at the first trigger point.
The second-most common pattern: a position is open when a high-impact news release (NFP, CPI, FOMC, EIA for crude oil) hits, and the price gaps through the stop and continues beyond the DLL threshold before the position can close at the intended price. The stop order fills at a worse price than set, and the total session loss at that fill already exceeds the DLL. In some cases the gap is large enough that even a correct stop placement would have resulted in a DLL breach — but more commonly, the stop was placed with insufficient buffer from the release window. The preventable version: if you are in a position going into a known high-impact window, close it before the release or set a firm rule to not be in a position in the 15 minutes before the scheduled event. Most news-gap DLL breaches happen in sessions where the trader was aware of the release but held anyway, intending to manage it reactively.
The third pattern is structural rather than behavioral: the DLL breach happens on the first trade of the session, often on a stop that would have been considered "normal" sizing in a different context, because the pre-session sizing check was not run. Specifically: the trader used a contract count that fit the DLL in earlier sessions when the trailing drawdown floor was further away, but the floor tightened through prior gains, and the same contract count now puts a single-stop loss at or above the DLL amount. Running the DLL ÷ 4 pre-session check at the start of every session catches this before the first entry — not after. The sizing error DLL breach is the most preventable of the three because it requires only one discipline: recalculate before opening, every session, without exception.
Part 4 of 4 — What to do
The DLL breach response is a three-step protocol — not a trading decision. The first decision you need to make after a breach is when to stop making trading decisions.
The moment the DLL triggers, close the platform interface, step away from the screen, and log the session within the next 30 minutes while the details are fresh. Log the entry, size, stop level, what the session's running loss was at the point you added or held, and which of the three patterns most closely describes what happened. Do not attempt to analyze the trade for alpha or method insight in this window — the goal is to capture the factual sequence (entry time, size, loss on each trade, what triggered each entry) before rationalization sets in. Analysis comes the next morning with a clear head. What you do immediately after the breach is the single largest factor in whether the evaluation continues or compounds.
Even if the platform technically allows re-entry after a DLL breach (which most do not), the psychological state following a DLL breach is the worst possible conditions for a trading decision. Loss aversion, urgency to fix the number, and the familiar feeling that "the market owes me" are all active. These exact states are what produced the breach in the first place, and they do not improve by staying at the screen. The correct posture for the rest of the trading day after a DLL breach is that the session is complete. The loss is real and it stays real. The evaluation or funded account continues the next session. There is nothing constructive that can be done with a funded account on the breach day that is not better done the following morning.
Before the next session opens, complete the three prevention steps in order: (1) Run the pre-session sizing check — your current balance, the current trailing drawdown floor, and what floor-distance you are working with. Recalculate your maximum per-trade risk (DLL ÷ 4) from today's numbers, not last week's. The breach may have moved your floor and reduced the floor distance materially. (2) Identify which breach pattern triggered yesterday's session. If it was the revenge pattern, add an explicit single-loss session stop to your pre-trade checklist: the session ends after the first trade that reaches the maximum per-trade risk. If it was a news gap, mark today's high-impact news releases and set a rule to be flat before each one. If it was a sizing error, confirm today's sizing math is complete before the first entry. (3) If you are in a funded payout account, re-read your firm's terms for post-DLL-breach trading requirements before opening your platform. Only proceed after you have confirmed the account is in a state where the next session is valid under your firm's rules.
In most cases, no — a DLL breach ends the trading session for that day but the evaluation continues the next trading day. The DLL is a per-session limit, not a per-evaluation limit in the typical funded futures model. What the breach costs is the day's loss and the trailing drawdown floor tightening from that loss. Some firms track repeated DLL breaches across an evaluation phase and may add a review step after multiple breaches, so check your firm's specific evaluation terms. But a single DLL breach in an evaluation typically does not reset or terminate the evaluation account.
The platform automatically closes any open positions and restricts new entries for the rest of that trading day. The exact mechanism varies by firm — some close positions at market and lock the account until the next session, others issue a warning at a threshold before the full DLL triggers. The breach is enforced in real time. If you are in an open trade when the DLL triggers, that position is closed by the platform, not by your stop order. Fill price is market price at the moment of breach, which in news-gap scenarios can be below your intended stop level.
On most funded futures platforms, the account is locked from new entries for the rest of that trading day once the DLL triggers. Some platforms define the "day" by calendar day, others by futures session boundary. A small number of firms technically allow re-entry after a DLL breach, but this is the exception. Even where it is technically available, attempting to trade back after a DLL breach compounds the risk. The psychological state after a breach — elevated stress, urgency to recover the loss — is the same state that produced the breach. The safest rule is to treat the day as finished when the DLL triggers, regardless of what the platform technically permits.
No. Trading back after a DLL breach is one of the most reliable ways to convert a recoverable evaluation setback into an account-ending event. The DLL breach loss is already real — trying to recover it same-session means adding more risk from the worst possible psychological starting point. The three breach patterns (revenge trading, news gap exposure, sizing error) are all more likely to repeat in the session after a breach than in any other session. The correct response is to log the session, end the trading day, and review root cause before the next session opens. The evaluation or funded account continues the next day. The loss does not get reversed by trading harder — it gets processed by trading smarter in the following sessions.
Three steps prevent most DLL breaches: (1) Run the pre-session sizing check every session — divide your DLL by 4 to get the maximum per-trade risk, then verify your stop distance times your contract count is at or under that number before opening. (2) Add a single-loss session stop to your trading plan: if one trade reaches the maximum per-trade risk, end the session. One maximally-sized loss puts you at 25% of the DLL; taking a second maximally-sized trade after that removes most of your cushion and leaves no room for error. (3) Mark your instrument's high-impact news windows — NFP, CPI, FOMC, EIA for crude oil — and have an explicit rule to be flat before each one. Most news-gap DLL breaches are avoidable with a 15-minute pre-release position close rule.
Once you're funded, your real education starts.
A DLL breach is a system check, not a character judgment. The Jalen Method covers the full stack: pre-session sizing discipline, the single-loss session stop, news-calendar rules, override capture, and the journaling practice that converts breach data into behavioral correction. First 100 founding seats at $19/mo — locked for life.