FxRobotEasy Editorial · Last reviewed
Failed Prop Firm Challenge — Honest Analysis of What Went Wrong
Illustrative composite scenario: This case study describes a representative outcome pattern observed across the FxRobotEasy user base. The trader alias, numbers, and narrative are composite rather than a single named account. Real verified live trading data is published on our /live-trading dashboard with Myfxbook syndication. Individual CRM-derived studies will replace these illustrative versions as trader permissions are documented.
Initial deposit
$100,000
Final balance
$0
Total return
-5.2%
Max drawdown
-5.2%
Win rate
55%
Profit factor
1.18
Trader profile
Alias: Trader B. (composite, anonymised)
Country: Brazil
Broker: FTMO simulated account, $100,000 two-step challenge, MT5 platform
Duration: 6 weeks (challenge failed before completion)
Period: September 2025 – October 2025
EA(s): scalperology
Trader B. attempted a prop firm challenge as their first serious EA deployment after running Scalperology on demo for 5 weeks. The failure occurred not because of EA malfunction or strategy failure, but because of an avoidable configuration error around news-event handling. We include this case study explicitly to show realistic failure modes and challenge the survivorship bias of EA marketing that only features successes.
Month-by-month equity progression
| Month | Start | End | P&L % | DD % | Trades | Notes |
|---|---|---|---|---|---|---|
| Week 1 | $100,000 | $101,800 | +1.8% | 1.2% | 22 | Good start |
| Week 2 | $101,800 | $103,200 | +1.4% | 1.9% | 24 | Steady progress |
| Week 3 | $103,200 | $105,100 | +1.8% | 2.4% | 21 | Trend favourable |
| Week 4 | $105,100 | $106,500 | +1.3% | 2.8% | 19 | Slowing — chop regime |
| Week 5 | $106,500 | $106,800 | +0.3% | 3.5% | 23 | Flat week before failure |
| Week 6 | $106,800 | $94,800 | -11.2% | 5.2% | 15 | CHALLENGE FAILED — daily DD violation during FOMC release |
Best illustrative trade
Week 3: LONG XAUUSD
Result: +158 pips (+2.8R)
Sustained gold momentum during London/NY overlap. The challenge was progressing well at this point with 6.8% gain vs 8% Phase 1 target.
Worst illustrative trade
Week 6: LONG XAUUSD
Result: −380 pips (−8R)
The failure event: a Scalperology entry triggered 45 seconds before FOMC rate decision release. The EA's news pause was configured for a 5-minute pre-news window — too short to capture this release timing precisely. The price gap during the FOMC statement produced -380 pip slippage well beyond the configured stop. This single trade exceeded the daily DD limit, automatically failing the challenge.
What worked
Strategy performance through weeks 1-5 was on target. The EA was on pace to hit the Phase 1 8% goal by week 7-8. Strategy edge was not the failure point.
Pre-challenge demo testing for 5 weeks gave Trader B. confidence in the EA's general operation. The challenge failure was an event-specific configuration issue, not a fundamental strategy problem.
FTMO's automated rule enforcement (instant daily DD detection and account closure) is unambiguous. There's no negotiation about the failure; the rule was violated, the challenge ended. This clarity is actually a feature — it's fairer than discretionary enforcement.
What didn’t work / could improve
The critical failure: Scalperology's news pause window was configured at 5 minutes pre-news, which is insufficient for FOMC-class events. FOMC announcements typically produce volatility 10-15 minutes before the official release due to early indications. The 5-minute window allowed a position to open 45 seconds before the release. Configuring 20-30 minute pre-news pause for high-impact events would have prevented this trade entirely.
Trader B. did not specifically review the news calendar for the challenge period in advance. FOMC week is well-known to be high-volatility; preemptively pausing the EA manually during FOMC week (or all of major news weeks) is a common prop-firm-challenge practice that wasn't adopted here.
The 5-week demo did not include FOMC week. Demo testing should include the highest-volatility windows the strategy will face in live operation; testing only during 'normal' weeks systematically underestimates the worst-case scenarios.
Lessons for readers
1. Prop firm rules favour conservative configuration
The 5.0% daily DD rule means a single bad trade can fail the entire challenge. Conservative position sizing AND aggressive news-event protection are both required. Configuring news pause windows generously (20-30 min pre-news for major events) protects against the failure mode that ended this challenge.
2. Demo testing must include the worst-case weeks
Five weeks of demo testing that excluded FOMC, NFP, and CPI releases produced false confidence. Demo periods should explicitly include at least 2-3 major news events to test news-handling configuration. This is the most common oversight in prop firm preparation.
3. Strategy quality is necessary but not sufficient
Scalperology's strategy edge was working through week 5. The failure was operational (configuration) not strategic (edge). EAs marketed as 'prop firm ready' still require user attention to the specific firm's rules and the specific news calendar during the challenge.
4. Survivorship bias dominates prop firm marketing
Most prop firm case studies feature passes. Statistically, the majority of attempts fail (~85% failure rate across the industry). This failure case represents what happens to most attempts — usually because of operational mistakes similar to the one shown here, not fundamental strategy issues.
5. Refund and re-attempt cost matters
The $540 challenge fee for FTMO $100K is lost on failure. Multiple attempts at conservative sizing (preferred for sustainability) cost more in cumulative challenge fees but reduce single-attempt blowup risk. Budget for 2-3 attempts when planning prop firm strategy.
“I want to be clear: this failure was my fault, not the EA's. Scalperology did exactly what it was designed to do for five weeks. I didn't configure the news pause correctly for FOMC week, I didn't review the news calendar in advance, and I didn't manually pause the EA before the release. Any of those three steps would have prevented this failure. The hardest part of writing this case study is admitting how avoidable the failure was. But that's why this case study exists — most EA marketing only shows successes, and that gives a misleading picture of what running EAs actually requires.”
See more case studies
8 case studies cover diverse outcomes including honest failures and drawdown recoveries.
Browse all case studies →