EA operations resources

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.

Cluster

Code Review

Tool path

mql5 code review

Reader

mq5 developer

Optional follow-up for MT5 EA backtest failure triage

Open the free desk first. Opt in only if this guide matches your compiler blocker for MT5 EA backtest failure triage.

Intent locked: Paste compiler errors

Lead activation handoff

No email wait is required. After saving the opt-in, continue into the free desk with the same blocker so the visitor-to-lead-to-workflow path is measurable.

Continue in free desk

Choose the workflow you want, then opt in only if you want Workfusionapp updates.

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.

Fix the first error first
Keep full EA context attached
Recompile before changing strategy logic

Related guides

Continue the EA build path.