Audience
For MQL5 builders whose EA compiles but order placement fails with invalid stops, rejected SL/TP, or retcode 10016.
MT5 execution blocker
Fix MT5 invalid stops without weakening the EA risk controls.
Diagnose MT5 invalid stops by checking Bid/Ask side, stop level, freeze level, spread, symbol digits, price normalization, and execution retcodes before manual retesting.
Common invalid-stops evidence
retcode=10016 invalid stops Buy SL >= Bid Sell TP >= Ask StopsLevel too close FreezeLevel active
These are execution validation failures, not proof that a strategy works or fails. Treat them as broker and symbol constraint evidence before the next manual test.
Debug retcode 10016 invalid stops
Check Bid/Ask side before SL/TP placement
Respect stop level, freeze level, spread, and symbol digits
Route opt-in source as invalid-stops fixer interest
Problem
Invalid stops usually mean the EA sends SL or TP on the wrong side, too close to price, not normalized to symbol digits, or incompatible with stop, freeze, or spread constraints.
Outcome
Workfusionapp keeps the repair path narrow: read live symbol constraints, validate stop distance, normalize prices, log retcode evidence, and reject unsafe trades 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. Check the stop side first
A buy stop-loss must sit below Bid and a buy take-profit above Ask. A sell stop-loss must sit above Ask and a sell take-profit below Bid.
2. Read live symbol constraints
Use the current stop level, freeze level, spread, point size, tick size, and digits before calculating distance or normalizing prices.
3. Reject unsafe trades instead of forcing orders
If the distance is invalid, log Bid, Ask, SL, TP, stop level, freeze level, spread, and retcode context, then skip the order until the setup is valid.
Workflow
From retcode 10016 to one validated stop-distance rule.
The fix is not to remove stops until orders open. The fix is to prove which constraint rejected the order, then make the EA reject bad distances before it sends the trade.
Step 1
Paste the retcode and order block
Step 2
Check symbol constraints
Step 3
Normalize and validate SL/TP
Step 4
Retest manually in Strategy Tester or demo
Invalid-stops handoff
Route the stop failure into the right execution check.
Open the guide that matches the failed constraint, then run the free desk with retcode, Bid/Ask, SL/TP, spread, and symbol settings.
Invalid stops guide
Use this when the EA compiles but SL/TP placement fails on side, distance, stop level, freeze level, or price normalization.
Spread filter guide
Use this when orders fail or should be blocked during wide spread, session changes, or broker-condition drift.
Fixed-risk lot sizing
Use this when stop distance, tick value, contract size, and lot step must agree before risk per trade is valid.
Send me the invalid-stops repair workflow
Opt in only if your MT5 EA compiles but order placement fails with invalid stops or rejected SL/TP. This captures the invalid-stops source for conversion measurement.
Intent locked: Paste compiler errors
Choose the workflow you want, then opt in only if you want Workfusionapp updates.
Does invalid stops mean the strategy is bad?
No. It means execution validation rejected the order parameters. Strategy review comes after the EA can produce valid, logged order attempts.
Should I remove SL or TP to make trades open?
No. Removing risk controls can hide the real issue. Fix side, distance, normalization, and symbol constraints first.
Does this require broker credentials?
No. Use code, Strategy Tester or demo logs, symbol settings, Bid/Ask, SL/TP values, and retcodes. Workfusionapp does not need broker login.