Audience
For MT4 and MT5 EA builders whose strategy needs a max-spread rule, broker-symbol guard, session-aware cap, and clear logs before prop-style or manual testing.
EA execution guard
Design an EA spread filter by measuring symbol spread, setting max-spread caps by session, logging blocked entries, and checking trade-count impact before prop-style testing.
Common spread-filter evidence
MaxSpreadPoints input missing Spread filter blocked every London setup CurrentSpread=38, MaxSpread=20 No log for symbol suffix or session Strategy Tester: 0 trades after spread cap
These are execution-control and observability issues. Fix measurement and logging before changing entries, lot sizing, or prop-style assumptions.
Audience
For MT4 and MT5 EA builders whose strategy needs a max-spread rule, broker-symbol guard, session-aware cap, and clear logs before prop-style or manual testing.
Problem
A spread filter can protect execution, but a random cap can also turn the EA into a silent zero-trade system. The unsafe pattern is blocking entries without logging current spread, cap, symbol, session, or how often valid setups are being removed.
Outcome
Workfusionapp keeps the review practical: measure spread on the actual symbol, set a cap by session or strategy window, log spread blocks once, compare trade-count impact, then route the EA into the risk checker.
Support path
Start with the concrete blocker, keep the full EA context attached, then move to a reviewable output.
Check the broker symbol, suffix, point size, digits, and session. XAUUSD, XAUUSD.raw, and index CFDs can require different spread caps.
When spread blocks an entry, log current spread, cap, symbol, session, and setup label once. Then compare how many setups survive the filter.
A spread cap should sit beside daily drawdown, max trades, cooldown, and invalid-stop guards. Do not let one filter hide every other blocker.
Workflow
The spread filter is a software control. It should make bad execution visible, preserve enough trade frequency for review, and avoid implying that a filtered EA is profitable or challenge-ready.
Step 1
Paste the entry and execution gate
Step 2
Measure spread by symbol and session
Step 3
Add max-spread block logs
Step 4
Retest manually with pass-rate evidence
Spread-filter handoff
Open the guide that matches the spread failure, then run the free desk with symbol settings, session window, current spread logs, max-spread cap, and tester trade-count impact.
Use this when the EA needs a max-spread guard, symbol-specific cap, session-aware rule, or spread-block logging before testing.
Use this when the spread cap may be one reason a compile-clean EA produces zero trades or silent tester runs.
Use this when spread, drawdown, exposure, cooldown, lot sizing, and tester evidence need to be reviewed together before manual use.
Send me the spread-filter workflow
Opt in only if your MT4 or MT5 EA needs a max-spread guard, session-aware spread cap, spread-block logs, or prop-style execution-readiness review. This captures the spread-filter source for conversion measurement.
Choose the workflow you want, then opt in only if you want Workfusionapp updates.
No. It is one execution guard. Prop-style readiness still needs drawdown, exposure, lot sizing, tester evidence, and manual rule review.
The cap may be too strict for the broker symbol or session. Log current spread, cap, symbol, and setup count before changing the strategy.
No. Use EA code, symbol settings, tester or demo logs, and manual account snapshots. Workfusionapp does not need broker login.