Prop Challenge Mistakes: Five Checks After an Incident

A losing trade, an unsuccessful evaluation, a contractual breach and an execution failure are different events. Reconstruct what happened before naming the cause. These are five review categories, not a measured ranking of the most common failures; this guide has no representative cohort for failure percentages or a promised improvement in pass probability.

1. Using the wrong loss calculation

Save the account’s balance, equity, open P/L, costs, reset time and applicable loss floor at the event. Read the exact provider/product/phase/cohort rule. A percentage of the displayed allocation is not automatically the remaining loss room, and an overall limit is not necessarily monthly or a peak-based trailing limit.

Do not count a stop order as a guaranteed fill or as proof the account cannot breach. Record the requested stop, actual fill, fees and other open exposure. If a threshold was reached, check its actual inequality and consequence rather than assuming another loss is allowed.

2. Assuming permission carries across accounts

FTMO’s news rules distinguish phases, account types, affected instruments and order execution, including stops and pending orders. A personal pause schedule or smaller position does not override a restriction.

FXIFY requires review and pre-approval for EA use on phased accounts. Check the exact file, platform, account and permission record. A licence does not authorise third-party operation or prohibited copying.

3. Changing size without tracking units and exposure

Record whether volume, stop distance, contract value or combined positions changed after a gain or loss. A fixed lot size is not fixed monetary risk when those inputs change. No universal 1% position rule, two-loss cooldown or “stop at 60%” threshold is established here.

Fictional sizing arithmetic: proposed gross stop-loss amount $500, stop distance 50 pips, assumed value $10 per pip for 1 lot. Volume = $500/(50 × $10) = 1 lot. A 0.1 lot volume gives a $50 gross stop loss under those assumptions, not $500. Verify real specifications, currency, volume steps, costs and execution; the example does not set a suitable risk amount or show rule compliance.

Separate fictional ledger: three realised losses of $200, $180 and $270 total − $650 before separate costs. They do not total − $450. A $400 loss is 32% of a $1,250 threshold, not 32% above it; account state and other losses remain necessary to assess the boundary.

4. Treating a test as proof

Keep data, costs, selected parameters, rejected trials and a separate evaluation period. MetaTrader documents historical optimisation and forward testing; neither guarantees future profit. Ten years, 100 trades or several positive months do not by themselves prove readiness or a universal edge. Mark any retuning and do not quietly reuse the same data as independent validation.

5. Confusing a gate with a breach

Read the exact wording of the unmet condition. FTMO’s 8 October update distinguishes 1-Step order/merge cohorts from 12 October and legacy Best Day rules. The denominator differs; the best day is not the same as the largest trade. An unmet consistency condition is not automatically a loss-limit breach. Read the complete rule and cohort instead of inventing an implicit equal-profit requirement.

An incident record you can act on

Keep unknown causes marked unknown. A correction to a calculation or configuration does not guarantee reinstatement or justify buying another attempt. A journal and a pause can support review; they do not establish a pass rate.

The JPTC EA Hub is separate from the hosted JPTC Algo: Algo customers install and run nothing and need no VPS. Neither product guarantees compliance, passing or payout. Company-published broker-statement figures are not a study of failed customer challenges or an independent audit.

Primary rule sources checked 16 October 2026.

JPTC Algo: company-published screenshots

Illustrative company screenshots, not evidence of challenge outcomes. Refer to the statement results page for the reported period.

@jptradingcapital on Instagram →