Code Review

Triage a failed MT5 backtest before changing the strategy.

A failed backtest does not automatically mean the strategy idea is bad. First classify the failure type: software, data, execution, risk gate, frequency, or edge.

Search intent

The user has a poor or broken MT5 backtest and wants a triage workflow.

Paste compiler errors / Generate EA draft / Get risk check

Short opt-in only. We store one source, one intent, and one new lead status. No scraped lists, no purchased contacts, no trading promises.

I agree to receive Workfusion EA builder updates and understand I can unsubscribe later.

Choose the workflow you want, then opt in so the CRM source is measurable.

Check if the EA traded enough

A two-trade backtest is usually not evidence. It may show over-filtering, data mismatch, or session/spread collapse.

Trade count

Trades per day

Blocked reason counts

Separate risk from edge

An EA can lose because sizing or stops are wrong even when entries have some signal value.

Max drawdown

Average loss

Stop distance

Lot calculation

Archive context

Always keep the report, set file, data range, symbol, and model together. Otherwise the result is hard to reproduce.

Report HTML

Set file

EA version

Date range

Use the tool

Use Workfusion to review the EA and create the next debug or optimization step.

Send me the EA workflow Open related tool page

Related guides

Continue the EA build path.

EA Generation

Prepare an EA for Strategy Tester

A practical checklist before running an MT5 Strategy Tester backtest on a new Expert Advisor draft.

Compiler Fixes

MT5 EA compiles but does not trade

A structured diagnostic checklist for MT5 Expert Advisors that compile but produce no trades.

Prop Firm Risk

Spread filter for prop firm EAs

Use spread filters to prevent an EA from entering during poor execution conditions without killing all trade frequency.