Code Review

Debug an MT5 EA that compiles but does not trade.

A zero-trade backtest can come from disabled trading, no historical data, strict filters, a signal that never triggers, invalid execution, or risk gates blocking every order. Treat it as an evidence problem, not a reason to loosen risk blindly.

Search intent

The EA compiles but produces zero trades or unexpectedly few trades in MT5 Strategy Tester.

Open compiler fix desk

Send compiler bundle

Optional follow-up for MT5 EA no trades debug checklist

Open the free desk first. Opt in only if this guide matches your compiler blocker for MT5 EA no trades debug checklist.

Intent locked: Paste compiler errors

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

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.

Confirm the EA is allowed to trade

Before changing strategy logic, verify the tester settings, symbol, timeframe, historical bars, auto-trading permissions, and account mode.

Correct symbol and timeframe

Enough bars and ticks

Trade permissions

Tester model and date range

Log every blocking gate

The EA should print why it skipped the tick: spread too high, session closed, max trades reached, risk guard failed, signal false, invalid volume, invalid stops, or unsupported filling mode.

Signal state

Spread filter

Session filter

Risk gate

Trade retcode

Test signal and execution separately

A valid signal can still fail execution, and a valid execution path can still have no signal. Keep those diagnostics separate so the next edit is based on proof.

Signal debug mode

One controlled test order in tester only

Retcode logging

No live-account action

Use the tool

Use Workfusion Backtest Estimate or MQL5 Code Review to turn a zero-trade run into a concrete next debugging step.

Fix the first error first

Keep full EA context attached

Recompile before changing strategy logic

Open compiler fix desk Open related tool page

Related guides

Continue the EA build path.

Code Review

MT5 EA backtest failure triage

Classify MT5 backtest failures by compile, data, permission, frequency, execution, risk, or strategy issues.

EA Generation

Prepare an EA for Strategy Tester

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

Code Review

MQL5 logging and diagnostics for EAs

Add useful MQL5 logs that explain EA decisions without flooding the MetaTrader journal.