Audience
For MQL5 builders whose EA compiles, loads in Strategy Tester or on a demo chart, but never reaches a real order attempt.
MT5 no-trades debugging
Find why an MT5 EA compiles but opens zero trades.
Diagnose an MT5 Expert Advisor that compiles but opens no trades by checking permissions, tester data, spread/session filters, signal frequency, risk gates, and execution retcodes.
Common zero-trade symptoms
Strategy Tester: 0 trades Signal=false for every tick Spread filter blocked retcode=10016 invalid stops retcode=10030 unsupported filling mode
These are different blockers. Treat zero trades as a pipeline: permissions, data, signal, filters, risk gate, execution, then retcode evidence.
Debug zero-trade Strategy Tester runs
Separate permissions, filters, signals, risk gates, and execution retcodes
Keep risk controls intact instead of forcing trades
Route opt-in source as no-trades debugger interest
Problem
Zero trades can come from disabled permissions, missing tester data, a signal that never becomes true, strict filters, invalid stops, unsupported filling mode, or a risk gate blocking every order.
Outcome
Workfusionapp turns the zero-trade run into a narrow debugging path: log the first block reason, separate signal from execution, keep risk gates visible, then run a focused review before manual testing.
Support path
One problem, one fix path.
Start with the concrete blocker, keep the full EA context attached, then move to a reviewable output.
1. Prove the EA is allowed to trade
Check tester date range, symbol history, Algo Trading permissions, account mode, and whether OnTick is logging before changing strategy logic.
2. Print the first block reason
Log only the first reason a tick is skipped: session closed, spread too high, max trades reached, daily drawdown guard, signal false, invalid stops, or unsupported filling mode.
3. Keep signal and execution separate
Count signal opportunities before testing order placement. If signals never occur, execution code is not the first blocker.
Workflow
From zero trades to one concrete block reason.
The goal is not to loosen every filter until trades appear. The goal is to prove which gate blocks the EA, then repair that gate without weakening the software workflow.
Step 1
Confirm tester data and permissions
Step 2
Log every blocking gate
Step 3
Measure signal frequency
Step 4
Review execution retcodes manually
No-trades handoff
Route the zero-trade run into the right evidence path.
Open the guide that matches the first proven blocker, then use the free desk with the smallest useful log bundle.
No-trades checklist
Use this when the EA compiles and loads, but Strategy Tester or demo produces zero entries after a full run.
Tester preparation guide
Use this when the issue may be symbol data, date range, tester model, input settings, or setup before code execution.
Logging diagnostics guide
Use this when the EA needs one clear block reason per tick instead of silent filters and unclear journal output.
Send me the zero-trade debug workflow
Opt in only if your MT5 EA compiles but does not trade. This captures the no-trades debugger source so we can measure whether the page creates qualified MQL builder leads.
Intent locked: Paste compiler errors
Choose the workflow you want, then opt in only if you want Workfusionapp updates.
Should I remove filters to force trades?
No. First log which filter or gate blocks the trade. Removing risk controls can hide the real software issue.
Does zero trades mean the strategy is bad?
Not always. It can mean permissions, data, signal frequency, broker constraints, or execution validation failed before orders were sent.
Does this require broker credentials?
No. Debugging no-trade behavior uses code, tester settings, logs, and retcodes. Workfusionapp does not need broker login.