MT4 Debugging

Fix MQL4 OrderSend error 130 with stop validation.

OrderSend error 130 usually means invalid stops. The EA may compile correctly, but the broker rejects SL or TP because price, distance, or normalization is wrong.

Search intent

The MT4 EA fails with OrderSend error 130 and needs stop-level validation.

Paste compiler errors / Generate EA draft / Get risk check

Short opt-in only. We store one source, one intent, and one new lead status. No scraped lists, no purchased contacts, no trading promises.

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

Choose the workflow you want, then opt in so the CRM source is measurable.

Validate stop direction

Buy and sell stops must be placed on the correct side of Bid and Ask. A wrong-side stop is rejected immediately.

Buy SL below Bid or Ask context

Sell SL above Ask or Bid context

TP on the opposite profitable side

Read broker stop level

MarketInfo can return minimum stop distance rules. Use them before calling OrderSend.

MODE_STOPLEVEL

MODE_FREEZELEVEL when relevant

NormalizeDouble with Digits

Reject instead of guessing

If the stop is invalid, log and skip the trade. Do not send random adjusted orders without recording why.

Log requested SL and TP

Log minimum distance

Log symbol and spread

Use the tool

Paste the MQL4 order block into Workfusion Debugger to get a cleaner draft and fix notes.

Send me the EA workflow Open related tool page

Related guides

Continue the EA build path.

MT4 Debugging

MQL4 compile errors cheat sheet

A quick guide to common MQL4 compile errors and the structural fixes to try first.

MT4 Debugging

MT4 EA magic number and order management

Use magic numbers, symbol filters, and order loops correctly in MQL4 Expert Advisors.

MT4 Debugging

Debug an EA that opens too many trades

Find duplicate-entry, missing cooldown, magic number, and signal-state issues in an EA that overtrades.