Trade Copier Not Copying Trades? The 9 Causes and Exact Fixes (MT4/MT5)

Short answer: when a trade copier stops copying, it is almost never the copier. Nine configuration causes account for essentially every case — and the first three (AutoTrading off, EA not running, terminals not on the same machine) cover most of them. Work through the list below in order; each item has a 30-second check and the exact fix.

The 9 causes, in order of likelihood

#	Cause	30-second check	Fix
1	AutoTrading off on the receiver	Top toolbar button red, not green	Click it green — on the slave terminal
2	EA not attached / not running	Chart top-right shows a sad face or nothing	Re-attach; enable "Allow algo trading" in EA inputs
3	Master and slave on different PCs	Local copiers need both terminals on one machine	Move both to the same PC or VPS
4	Symbol name differs between brokers	XAUUSD on master, GOLD or XAUUSD.a on slave	Add a symbol map: XAUUSD=GOLD
5	Copied lot below broker minimum	Journal shows "invalid volume"	Raise multiplier or use fixed lot ≥ 0.01
6	Receiver is a netting account (MT5)	Account type in terminal title says "netting"	Use a hedging account for the slave
7	Master account not whitelisted on slave	Slave's MasterAccounts input excludes it	Add the master's account number or leave blank
8	WebRequest URL not allowed	Dashboard shows the terminal offline (copy still works locally)	Tools → Options → Expert Advisors → add the URL
9	Market closed / symbol not tradable on slave broker	"Market closed" or "trade disabled" in Journal	Nothing to fix — check the slave broker's symbol hours

Cause 1–2: nothing is running

Before touching any setting, look at the receiving terminal. The AutoTrading button in the toolbar must be green — on the slave, not just the master. Then look at the chart's top-right corner: the EA's name with a smiling face means it is running; a sad face means the terminal refused it (usually algo trading disabled in the EA's own Common tab). No name at all means the EA is not attached. This is the cause in well over half of "not copying" reports, and it is embarrassing precisely because it is so simple.

Cause 3: the terminals cannot see each other

A local copier passes trades between terminals through files on the same machine — that is what makes it millisecond-fast and independent of your internet. The flip side: master and every slave must be on the same PC or VPS. If you set the master up on your desktop and the slave on a VPS, they are on different planets. Move them together. (A cloud copier does not have this constraint — but it has the latency and the outage risk instead.)

Cause 4: the silent one — symbol names

This is the cause behind "it copies some trades but not others". Brokers name the same instrument differently: XAUUSD, GOLD, XAUUSD.a, XAUUSDm, GOLD.i. When the master trades a symbol the slave's broker calls something else, a copier with no mapping either skips the trade silently or logs "unknown symbol" in the Journal — which nobody reads. The fix is a symbol map on the receiver, one line per difference: XAUUSD=GOLD;GBPUSD=GBPUSD.a. Most copiers also have a suffix setting for brokers that append the same suffix to everything. Ours calls them SymbolMap and SymbolSuffix — the setup guide lists both.

Cause 5–6: the broker refuses the order

Lot below minimum. If the master trades 0.05 and your multiplier is 0.1, the copy is 0.005 — below any broker's minimum, so it is rejected with "invalid volume". Either raise the multiplier or switch to a fixed lot. Netting accounts. On MT5, a netting account merges every position on a symbol into one — so a master with two separate GOLD longs cannot be mirrored one-to-one, and closes get confused. Slaves should be hedging accounts; most brokers let you choose at account creation.

Cause 7–9: rules and reality

If the receiver's MasterAccounts filter is set, it only follows the listed account numbers — a typo there means silence. The WebRequest URL matters only for the dashboard: with it missing, copying still works locally, but the terminal shows offline on the web. And sometimes there is nothing wrong at all — the slave's broker has the symbol closed, or disabled for trading, when the master fired. The Journal says so; the copier cannot override the broker.

A five-minute diagnostic that finds it every time

1. On the slave terminal: AutoTrading green? EA smiling? If not, that is it.
2. Open a 0.01 trade on the master on EURUSD — a symbol every broker names identically. Does it copy? If yes, your problem is symbol mapping on the symbol that did not copy.
3. Read the slave's Journal and Experts tabs for the last minute. "Invalid volume", "unknown symbol", "trade disabled" each name the cause outright.
4. Check the copier's own status: on ours, the dashboard shows each terminal online/offline and every copy event with its result and delay — a failed copy appears with the broker's error text.

When it is the copier's fault

Rarely — but a copier that does not mirror a given event type cannot be configured into doing so. Before choosing one, ask specifically: does it copy pending orders? SL/TP modifications? Partial closes? MT4→MT5 and back? If any answer is no, that is a trade type you will lose. The honest list for the CopyConnectFX copier is on the trade copier page; the cross-platform guide covers the MT4↔MT5 specifics.