A funded account breach doesn't feel like a paperwork event. It feels like a phone call you didn't get. One moment you're holding a position, the next the account shows flat, the fill price is worse than anything you'd have chosen, and the dashboard says the account is "under review." What actually happened in that gap, and who made the decision to close your trade, is a mechanical question most funded-account marketing pages never answer. This walks through the operational mechanics: what triggers an automatic flatten, what doesn't, what happens to the account afterward, and why running a copier across multiple funded accounts adds a failure mode most traders never think about until it happens to them.
When a funded account hits a hard breach, such as a daily loss limit or maximum drawdown violation, most funded-account providers and margin platforms are built to automatically flatten (force-close) all open positions the instant the breach is detected, at whatever price is available at that moment, not a price the trader picks. This isn't universal: some breach types, like a soft consistency-rule flag, pause new order entry without closing existing positions, and the exact trigger and mechanics vary firm to firm, so check your own provider's rulebook rather than assuming a standard behavior. For a trader running a copier across multiple funded accounts, the practical danger is that the copier's own internal record of that account can go stale the instant the firm's risk engine closes the position, entirely outside the copier's control.
Does a Prop Firm Close Your Trades Automatically After a Breach?
In most cases yes, but only for what's usually classified as a hard breach, and the exact behavior is set by the individual firm, not by any outside regulator. Funded account programs typically run on simulated or evaluation capital rather than a traditional regulated brokerage account, so there's no single body like the CFTC, NFA, SEC, or FINRA mandating exactly how or when a provider must close a position after a breach. Each firm writes its own risk engine and its own rulebook, and those differ from provider to provider.
That doesn't mean forced, no-consent liquidation is unusual or specific to prop trading. It's a long-standing structural feature of leveraged trading generally. Under FINRA's own Rule 2264 (Margin Disclosure Statement), which governs margin accounts at FINRA-regulated broker-dealers, a broker-dealer can liquidate a customer's positions to meet a margin call without contacting the customer first, and the customer doesn't get to pick which position gets sold. Retail trading platforms enforce the same idea mechanically: MetaTrader 5's own documentation describes Stop Out as a server-side process that, in its standard (non-FIFO) mode, automatically closes the position carrying the largest loss first, per MetaQuotes' terminal help documentation, and it isn't the trader who picks which position closes. A funded-account provider's risk engine, watching a daily loss limit or a drawdown line instead of a margin-level percentage, is applying the same basic pattern: once its threshold is crossed, the firm's system decides, not the trader.
Soft Warning vs Hard Breach: Two Very Different Outcomes
Not every rule violation ends with your positions getting closed. It helps to think of funded-account risk enforcement in two tiers, even though firms don't always use this exact language.
A soft warning or restriction is typically triggered by something like a consistency-rule flag, for example a single trading day contributing an outsized share of total profit. This usually pauses new order entry or flags the account for review, but it commonly does not force-close whatever positions are already open at the time. The rule mechanics behind these flags, why they exist and how the math is usually calculated, are covered in our breakdown of prop firm consistency rules, worth reading before assuming a flag on your account means an open trade is about to get closed.
A hard breach is different. A daily loss limit hit or a maximum or trailing drawdown breach is usually treated as an immediate, account-level risk event, and this is the category that commonly triggers an automatic flatten of everything open. But "commonly" is doing real work in that sentence. Some firms review before acting on smaller breaches. Some treat every drawdown breach identically regardless of position count or size. Some distinguish between a breach detected intraday versus one only confirmed at end-of-day settlement. None of this is standardized, so the only way to know how your specific account behaves is to read your firm's own rulebook, not to assume it matches what a forum post or a competitor's terms say.
How Does a Forced Flatten Actually Execute?
Mechanically, a hard-breach flatten works the same way a margin stop-out works: the risk engine watches an account-level number continuously, often on every tick or price update, and the instant that number crosses the configured line, it doesn't wait for you and it doesn't wait for a better price. It sends a market order, or a series of them if you're holding multiple positions or contracts, to close everything, and that order fills at whatever price the market is offering in that moment.
That gap between detection and execution, however small, means the price you actually get closed out at is very often worse than the theoretical price implied by your loss limit. Here's a worked example using illustrative numbers only, not any specific firm's actual published limits.
Say a funded account has $1,000 of remaining daily-loss cushion before it hits a hard breach. You're long 2 ES contracts entered at 5,600.00. ES carries a well-established $50 multiplier per index point, per CME Group's own contract specifications (verify the current figure directly with CME Group or your broker before relying on it). The risk engine marks the account breached the instant open-trade loss reaches $1,000, which happens at $1,000 / (2 contracts x $50/point) = 10.00 points of adverse movement, putting the theoretical breach price at 5,600.00 minus 10.00, or 5,590.00.
But the flatten order doesn't fill at 5,590.00. It fills at the next price the market actually offers after the order is sent, and in a fast-moving market that can be meaningfully worse. If the fill lands at 5,588.50, that's an extra 1.50 points of adverse slippage, costing 1.50 x 2 contracts x $50/point = $150.00 beyond the nominal limit. The total realized loss becomes 11.50 points (5,600.00 minus 5,588.50) x 2 contracts x $50/point = $1,150.00, which is $150.00 worse than the $1,000 cushion the trader thought bounded their downside.
What Is the Margin-Level Stop-Out Mechanic, and Why Does It Matter Here?
Retail trading platforms like MetaTrader and cTrader use a slightly different metric than a daily-loss dollar figure, margin level, but the enforcement logic is identical, and understanding it makes the prop-firm version easier to reason about.
Margin level is calculated as Margin Level % = (Equity / Used Margin) x 100. Take an account with a $10,000 balance and $2,000 used margin. With no floating loss, equity equals balance, so margin level is ($10,000 / $2,000) x 100 = 500%, far above any typical warning threshold. Now say floating losses grow to $1,000: equity drops to $10,000 minus $1,000, or $9,000, and margin level becomes ($9,000 / $2,000) x 100 = 450%, still comfortable. If losses deepen further so equity falls to $1,000 (a $9,000 floating loss), margin level becomes ($1,000 / $2,000) x 100 = 50%. If the broker's configured stop-out level is 50%, that crossing triggers an automatic closure at that exact instant, with no confirmation step and no human in the loop.
Per cTrader's own Help Centre documentation, the stop-out level is a margin-level percentage set "solely by your broker," and once account margin level falls to or below it, the platform begins closing positions automatically: either a full "fair" closure of the position carrying the largest margin usage, or a partial "smart" closure sized just large enough to restore the margin level above the line. MetaTrader 5 works the same way structurally: Stop Out is server-side and, per MetaQuotes' documentation cited above, closes the position with the largest loss first in normal operating mode.
The table below lays out the general two-tier shape this takes across most leveraged platforms, using illustrative numbers, since actual thresholds are broker-configured and not standardized.
| Tier | Illustrative trigger | What typically happens |
|---|---|---|
| Margin call / warning | e.g. margin level falls to 100% | New position restrictions or a warning notice; existing positions are typically left open |
| Stop out / forced liquidation | e.g. margin level falls to 50% | Platform automatically closes position(s), largest-loss or largest-margin first, no confirmation required |
| Prop-firm hard breach (analogous pattern) | e.g. daily loss limit or max drawdown reached | Firm's risk engine typically force-flattens all open positions; exact behavior is firm-specific |
Once a hard threshold is crossed, the risk engine decides when your position closes, not you.
A prop firm's daily-loss or drawdown-based risk engine watches a different number than margin level, but it's the same operational shape: continuous automated monitoring against a hard line, with an automatic close the instant that line gets crossed. That's why the ES example above and the margin-level example above produce the same practical lesson even though the specific metric differs. The number that matters is whichever one your firm has chosen to enforce, and the only reliable way to know it is to read your firm's current rulebook, not to assume your account works like a default margin calculation.
The Hidden Risk for Multi-Account Copy Traders: State Desync
Everything above applies to a single account. Running a copier across multiple funded accounts adds a failure mode that has nothing to do with the flatten itself and everything to do with what happens to the copier's own record-keeping afterward.
Here's the scenario. A trader runs a copier managing three funded accounts, call them A, B, and C, and opens 1 NQ contract short, mirrored to all three at roughly the same time. Minutes later, Account B's own drawdown risk engine, independent of this specific trade and driven by that account's cumulative daily P&L across everything it's holding, detects a hard breach and force-flattens Account B. The short NQ position on B gets closed at whatever price is available at that moment, and B's resting stop-loss order, if the platform cancels it, disappears along with it.
The copier's internal record for Account B, however, still says "short 1 NQ" until the copier's next reconciliation check against the broker's actual reported account and position state. That gap, however short, is where the risk lives. If the copier acts on its stale internal record during that window, for example trailing a stop or applying a partial close instructed by a later adjustment on the leader account, it's issuing instructions against a position that no longer exists on Account B. Depending on how that specific broker's API handles orders sent against a flat account, the result is one of three outcomes: the order errors out, it silently no-ops, or in a worst case it gets accepted as a brand new position in the opposite direction of what was intended.
This is the same broader category of multi-account timing risk covered in our piece on sync and slippage risk across multiple copied accounts, applied specifically to the case where one account's state changes because of the firm's own risk engine rather than because of a market move.
What Should a Well-Built Copier Do When This Happens?
Be direct about the limit here first: no copier, including Thor, can prevent a firm's forced flatten from happening. That decision is made entirely inside the firm's own risk system, on the firm's own account, based on the firm's own numbers, and it happens outside the copier's control by design, the same way a broker's stop-out or a clearing firm's forced liquidation happens outside a retail trading platform's control. If your account's drawdown or daily loss triggers a breach, the firm is going to close the position regardless of what any copier software does or doesn't do. Anyone claiming otherwise is selling something that doesn't exist.
What good copier engineering can do is get the aftermath right, and there are three specific things that matter.
First, detect the discrepancy quickly, and detect it correctly. That means treating the broker's reported account and position state, pulled directly on a reconciliation pass, as the source of truth, not the copier's own last-known internal record. A copier that trusts its own memory over the broker's live state is the exact failure mode described above.
Second, stop attempting to manage a position the firm's risk engine already closed. Once reconciliation shows Account B is flat, the copier needs to drop any pending instructions still queued against B's old position, trailing stops, partial closes, scale-outs, rather than sending them anyway and hoping the broker sorts it out.
Third, alert the trader. A silent no-op or a silently swallowed error is worse than doing nothing, because it leaves the trader assuming their multi-account setup is still working as intended when one leg of it quietly isn't. The right behavior is a clear, immediate notice: this account was force-closed outside the copier's control, here's what was detected, here's what the copier stopped trying to do.
None of this changes whether the firm flattens the account. It changes whether the trader finds out from their own copier within moments, with an accurate picture of what happened, or finds out later from the broker's own dashboard after the copier already tried and failed to manage a position that wasn't there.
Are Pending Orders and Stop-Losses Canceled Too?
This is one of the most firm-specific and least documented parts of the whole process, worth checking directly with your provider rather than assuming either answer. Some platforms cancel every resting order tied to the account or the affected symbol the moment a forced flatten executes, on the reasoning that an orphaned stop-loss attached to a position that no longer exists serves no purpose. Other setups leave pending orders resting, which creates its own problem: a stop-loss or limit order that was protecting a now-closed position can sit there un-triggered, or in some configurations get treated as a fresh order if the underlying position it was attached to no longer exists to reference.
Whether pending orders survive a flatten, and what happens to them if they do, is platform- and firm-specific behavior. Confirm it directly with your provider's support desk or rulebook rather than assuming your stop-loss automatically disappears, or automatically stays live, after a hard breach.
Don't assume a resting stop-loss or take-profit order automatically disappears along with a force-closed position. Verify your specific firm's and platform's behavior before treating a pending order as canceled.
Is the Account Suspended, or Is It Permanently Closed?
After a hard breach, account status generally falls into one of two buckets, and which one applies to you is entirely a matter of your firm's policy, not a universal rule.
Some providers suspend the account pending review. The breach triggers the flatten, the account is frozen from further trading, and a human or an automated review process confirms the breach before a final decision is made, sometimes with a path to reinstatement or a second evaluation attempt depending on the specific program's terms. Other providers close the account immediately and treat the breach as final the moment the automated system detects it, with no review step and no reinstatement path.
Neither approach is inherently more common industry-wide; it depends entirely on the specific firm's business model and terms. If your account survives review, or you're offered a chance to rebuild toward funded status again, the underlying math of how a drawdown recovers, or doesn't, after a loss is a separate and important question, covered in detail in our piece on drawdown recovery math for funded accounts. Read your specific account agreement for the actual answer on suspension versus permanent closure. This isn't something to infer from a forum thread or a competitor's policy.
Do You Still Have Access to the Account Afterward?
This also varies. Some platforms leave the dashboard visible in a read-only state so you can review your trade history, closing prices, and the specific breach event that triggered the flatten. Others restrict or fully revoke login access the moment the account closes, which can make it harder to reconstruct exactly what happened, what price the forced close filled at, and whether any pending orders were affected.
If preserving that visibility matters to you, and it should, check it before you fund an account rather than after a breach. Ask the provider directly, or read the account agreement, whether a suspended or closed account remains viewable and for how long. This single detail affects how easily you can verify the mechanics described above actually happened the way your provider says they did.
Frequently asked questions
Does a prop firm automatically close my trades when I breach a rule?
In most cases yes, but only for what's typically classified as a hard breach, such as a daily loss limit or maximum drawdown violation; a soft warning like a consistency-rule flag often restricts new trading without closing existing positions. The exact trigger and behavior are set entirely by the individual firm's own risk engine, so confirm the specific rules in your firm's account agreement rather than assuming a universal standard. This mirrors how regulated margin accounts work too, where a broker can liquidate positions to meet a margin call without asking first.
What price do my positions close at when a funded account gets force-flattened?
Positions close at whatever price is available in the market the instant the flatten order executes, not at the theoretical price implied by your loss limit. Because there's a detection-to-execution gap, however brief, the realized loss can come in worse than the nominal limit you thought bounded your downside, similar to slippage on any market order. In an illustrative example with a $1,000 loss-limit cushion on 2 ES contracts, a fill landing 1.5 points past the theoretical trigger price alone adds $150 of extra loss (1.5 points x 2 contracts x $50 per point).
Is a consistency-rule violation the same as a drawdown breach?
No, these are usually treated very differently. A consistency-rule flag is commonly a softer restriction, for example pausing new order entry, while a drawdown or daily-loss breach is commonly a hard, account-level event that triggers an automatic flatten of open positions. Our breakdown at /blog/prop-firm-consistency-rules-explained covers the mechanics behind the softer category in detail. Which category a given rule falls into, and what it does to open positions, is set independently by each firm.
Do pending stop-loss orders get canceled when a funded account is flattened?
This depends entirely on the platform and firm, and there's no universal answer. Some systems cancel every resting order tied to the account or symbol the moment the flatten executes, while others leave pending orders resting, which can create orphaned orders attached to a position that no longer exists. Confirm this specific behavior directly with your provider before assuming either outcome.
Will my funded account be permanently closed after a breach, or can it be reinstated?
This is a firm-specific policy choice with no industry standard. Some providers suspend the account pending a review process, sometimes with a path back to funded status, while others close the account immediately and treat the breach as final the moment it's automatically detected. Read your specific account agreement to know which model applies to you, and see /blog/drawdown-recovery-math-funded-accounts for the math behind rebuilding after a loss if reinstatement is on the table.
Can I still see my account and trade history after it gets breached?
It depends on the platform. Some providers leave the dashboard visible in a read-only state so you can review the closing price and breach details, while others restrict or revoke login access as soon as the account closes. Confirm this detail with your provider before you fund an account, since it affects how easily you can verify exactly what happened during a forced flatten.
How does a margin call differ from a stop out?
A margin call is typically a warning level, for example when margin level falls to around 100%, that restricts new trading but usually leaves existing positions open, while a stop out is the lower, forced-liquidation threshold where the platform automatically closes positions with no confirmation needed. Per cTrader's own documentation, this stop-out level is a margin-level percentage set solely by the broker, and MetaTrader 5 similarly processes Stop Out server side, closing the largest-loss position first in its standard mode. Prop firms apply the same two-tier shape to daily-loss or drawdown numbers instead of margin-level percentages, though the specific thresholds are firm-defined.
If I run a copier across multiple funded accounts, what happens when just one account gets force-flattened by its firm?
The firm's flatten only affects that one account directly, but it creates a state mismatch risk for the copier managing it, since the copier's internal record can still show a position as open on that account until its next reconciliation check against the broker's actual state. A well-built copier needs to detect that mismatch against the broker's live data, stop issuing instructions against the now-closed position, and alert the trader immediately rather than silently continuing to act on stale information. See /blog/multi-account-copy-trading-sync-slippage-risk for more on the broader category of multi-account timing risk.
Can a trade copier prevent a prop firm from force-closing my position?
No, the forced flatten is a decision made entirely inside the firm's own risk system, on the firm's own numbers, and it happens outside any copier's control by design, the same way a broker's own stop-out mechanism operates outside a trading platform's control. What good copier engineering can do is detect the resulting account-state change quickly and accurately afterward, rather than prevent the flatten itself. No software sitting outside the firm's own systems has the authority to override that decision.
Can I close my own positions before the risk engine forces a flatten?
Yes, in nearly every setup you can manually close a position at any point before your account crosses the firm's hard-breach threshold, which gives you control over your own exit price instead of leaving it to whatever the market offers during an automatic flatten. The catch is timing: the risk engine is typically watching the same numbers you'd need to track yourself, such as remaining daily-loss cushion or distance to a drawdown line, so you need to know your own real-time exposure before it crosses the threshold, not after. Watching your own account-level P&L against the firm's stated limits, rather than waiting for the platform to act, is the only way to guarantee you pick your own exit instead of the risk engine picking it for you.