MT4 Debugging

Use magic numbers so your MT4 EA manages only its own trades.

An MT4 EA without disciplined magic number filtering can close, modify, or count trades it does not own. That makes testing unreliable and live use dangerous.

Search intent

The developer needs to prevent an MT4 EA from managing the wrong trades.

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.

Filter by symbol and magic number

Every order loop should check both symbol and magic number before counting, closing, or modifying positions.

OrderSymbol equals chart symbol

OrderMagicNumber equals EA input

Skip manual or unrelated orders

Count exposure correctly

MaxOpenTrades should count only the EA's own trades unless the rule intentionally covers all exposure.

Separate own trades from account exposure

Log count source

Avoid duplicate entries

Make ownership visible

Use comments and logs to make it clear which EA instance created or modified each trade.

Order comment prefix

MagicNumber input

Symbol-specific logs

Use the tool

Run Workfusion MT4 Debugger to flag missing symbol and magic number filters.

Send me the EA workflow Open related tool page

Related guides

Continue the EA build path.

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.

MT4 Debugging

Fix OrderSend error 130 in MQL4

Diagnose invalid stops, stop level, digits, and price normalization issues behind MQL4 OrderSend error 130.

MT4 Debugging

MQL4 compile errors cheat sheet

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