Your Prop Firm's Risk Engine Is Not Your Safety Net
On September 26, a trader posted on r/PropFirms that his FundingPips master account, one day from payout, was closed on a trade floating -$145. He believed his 4% daily allowance was $400. The engine, running its own math on its own feed, disagreed with all of it. If you read that as a story about one firm, you miss the actual lesson. The risk engine was never on his side, and it is not on yours. It is an enforcement layer, and the difference between enforcement and protection decides how you should size every trade you place on a funded account.
Key Takeaways
- The engine enforces; it does not protect. It polls equity on the firm’s feed, compares it to the firm’s floor, and liquidates at market when the floor is crossed. Your stop-loss is not part of that loop.
- Detection is definitionally after the fact. A breach has to exist before the engine can see it. Whether liquidation lands in a blink or a few seconds later, on a hard-breach plan the breach has already printed.
- The same liquidation means opposite things. On a FundingPips master account it is a hard breach and the account is gone. On an Apex 50K EOD account the $1,000 daily loss limit is a soft breach: session over, account alive.
- The closing print can be worse than your stop. Liquidation fires at market through whatever spread and depth exists at that moment.
- The layer that protects you is the one you run. A guard set inside your own line, inside the firm’s floor, with real daylight between all three.
What the September Case Actually Shows
The full arithmetic lives in the FundingPips breach breakdown, so here is only what matters for this argument. The trader computed his 4% daily limit off a $10,000 balance: a $400 allowance, a $9,600 floor. The firm’s help center actually measures the limit from “the higher of opening balance or equity.” His account opened green at $10,272, so the enforced floor was $9,861.12 and the real allowance $410.88. His open trade was auto-closed at -$145 floating, a number that fits neither floor cleanly, and the account was suspended.
His model of the rule and the engine’s model were different objects, and only one of them had delete permissions. That is the whole case in one sentence. Every protection he thought he had, the $400 of room, the stop he would have moved, the payout one day away, lived in his model. The engine does not poll your model.
What a Risk Engine Actually Does
A prop firm risk engine runs a poll cycle on its own market feed, builds equity from balance plus every floating position, compares it to a floor computed on the firm’s own definition of the base, and liquidates at market when the two touch. It watches no price level you chose, waits for no order you placed, and answers to no session you planned. None of this is hidden. The “higher of opening balance or equity” language is in the help center, and the firm’s own blog notes that unrealized losses count against the daily limit. It is written in compliance English, and the gap between reading the rule and pricing the rule is where accounts die.
Notice what the engine has in common with your stop-loss and what it lacks. Your stop becomes a market order when your price trades. The engine becomes a market order when its number crosses. Different data, different clock, different priorities. When the two disagree about where the account stands, the engine wins, because the engine is the one writing the breach record.
Detection Is Definitionally Late
Traders spend a lot of energy arguing about enforcement latency, as if the danger were that the engine acts too slowly. The direction of the problem is the opposite. The engine’s trigger condition is the breach. Equity has to touch the floor before there is anything to detect, so the engine cannot close you before the breach in any sense that helps you. It can only close you after, quickly or slowly, and hand you the record.
That means racing the engine with faster execution is the wrong race entirely. Suppose its liquidation lands half a second after the floor prints, suppose it lands three seconds after. On a plan where the daily breach is fatal, the outcome is identical: the breach exists, the account is gone, and the only open question is how ugly the final ticket looks. The September case closed at -$145 against an assumed $400 of room, which tells you the engine’s version of events did not need to be fast. It needed to be authoritative, and it was.
So the useful question is never “how fast is their engine?” It is “what stands between my trade and their floor?” On most funded accounts, the honest answer is nothing.
Soft Breach, Hard Breach: Same Liquidation, Different Funerals
One more thing the engine does not carry: mercy, or its absence. Whether an auto-liquidation ends the account or just ends your morning comes from the plan’s consequence line, which the engine applies without reading the room.
| Limit | Typical size | Breach type | What the liquidation means |
|---|---|---|---|
| FundingPips daily drawdown (master) | 4% of the higher of balance or equity | Hard | Account terminated; the -$145 close ended a payout-ready account |
| Apex 4.0 daily loss limit (EOD) | $1,000 on a 50K | Soft | Positions liquidated, session locked out, account continues tomorrow |
| Apex trailing drawdown | $2,000 on a 50K, locks at $50,100 | Hard | Account failed |
| FTMO 2-step max loss | Static 10% of initial capital | Hard | Account failed; equity below $90,000 on a $100K ends it any day |
The same forced-liquidation event is a bad morning on one plan and the end of the account on another. You find that out from the terms, before you size, or from the engine, after. The first way is cheaper.
Three Layers Between You and the Floor
Everything that can act on your position sorts into three layers, and only one of them is trying to keep you under the firm’s limits rather than to enforce them.
| Layer | Watches | Acts | Worst case |
|---|---|---|---|
| Your stop-loss | A price level you chose | At your broker, on price | Gaps through on news; protects you from the market only, never from the firm |
| The firm’s engine | Its floor, its feed, floating included | At or after the breach, at market | Print lands worse than your stop; on hard-breach plans the account dies with it |
| Your own guard | Your line, inside the firm’s floor | Before the breach, continuously | A small realized loss, inside the budget you chose |
The third layer is the one most funded traders never install. A stop-loss protects you from the market. The firm’s engine enforces the firm’s rulebook. A guard you run yourself, on your own terminal, watching your own line, is the only layer whose job is to keep you out of the first two’s way. That is the whole premise of equity guard trading, and it matters most on the account types where the firm’s floor sits closer than it looks, the shadow drawdown problem.
Building the Guard That Fires First
The setup takes minutes and it is the same on any plan:
- Write the firm’s true floor, not the advertised one. Equity basis, floating included, green-open base raise. If the account can open green, assume the floor opens higher.
- Set your own line 20% inside it. On a $1,000 daily loss limit, the guard fires at -$800. On a $2,000 drawdown budget, cut yourself off with $300 unspent. The daylight is what absorbs gaps, spread, and the engine’s own poll interval; the buffer-first sizing math treats that daylight as the account you are actually trading.
- Let the guard, not willpower, own the number. An equity-touch limit like Apex’s DLL is breached by a tick of floating loss, mid-second. The auto-close guard exists because no human closes a position that fast, session after session.
- Shrink size instead of stretching the guard on event days. A CPI or NFP candle can clear an entire buffer band in one print, which no guard setting fixes. On those mornings the only defense that works is the one you choose at the sizing stage, smaller or flat, the way the daily loss limit guide puts it.
None of this makes the firm’s engine your friend. It makes the engine irrelevant, which is the closest thing to safety a funded account has. The Apex 4.0 numbers make the stakes concrete: at $250 risk, four stops burn the DLL; at $150, six or seven fit under it. Size so the guard fires on your fifth mistake, not the firm’s first.
Put a guard between your trades and their engine
ChartWise watches your equity against limits you set, on MT4 and MT5, and closes positions before the firm’s floor is ever in play. From the desk or your phone.
Get Early Access →Frequently Asked Questions
Does the prop firm risk engine close positions before the breach?
No. The engine's trigger condition is the breach itself: equity touching the firm's floor on the firm's own feed. Detection therefore happens at or after the breach, and the liquidation lands afterward, at market. A fast engine hands you a printed breach quickly; it never hands you a save.
Why was my position closed at a loss smaller than my daily limit?
Because the allowance the engine enforces is not always the one you computed. In the September FundingPips case, a trader reading the 4% daily limit off a $10,000 balance expected $400 of room and was closed at -$145 floating, while the firm's base sat at $10,272 equity, which puts the floor at $9,861. Floating losses count, the base can sit above your balance, and the engine polls its own numbers.
Is a daily loss limit breach always fatal?
No, and the difference matters more than the percentage. On an Apex 50K EOD account the $1,000 daily loss limit is a soft breach: positions are liquidated for the session and the account continues. On a FundingPips master account the equivalent close is a hard breach and the account is gone. Read the consequence line of your plan, not just the size of the limit.
How much buffer should I leave above the firm's floor?
Roughly 20% of the daily limit, so a guard at -$800 on a $1,000 daily loss limit, and at least $300 of unspent drawdown budget on a $2,000 max drawdown. More on event days: a CPI or NFP candle can jump an entire buffer band in one print, so the only real defense that morning is smaller size or flat.
The Short Version
- The risk engine is an enforcement layer: it polls equity on the firm’s feed, against the firm’s floor, and liquidates at market when they touch.
- Detection is definitionally after the breach. Racing the engine is the wrong race; on hard-breach plans the printed breach ends the argument regardless of latency.
- The September FundingPips close at -$145 against an assumed $400 allowance is what it looks like when your model of the rule and the engine’s model differ.
- Soft and hard breaches share the same liquidation and nothing else: read the consequence line before you size.
- Guard at 80% of the daily limit, keep $300 of drawdown budget unspent, and size smaller on event days. The layer that protects you is the one you run.