Why Your Trade Copier or EA Suddenly Stopped Working

When an EA or trade copier stops copying trades with no error message, the cause is almost always one of a handful of silent failures on the terminal, VPS, or signal source. Here's the order to check them in.

You check the chart and the last trade sits there from hours ago. No new positions have opened, no error box has popped up, and nothing in the terminal looks obviously broken. This is the most frustrating version of a trade copier stopped working: there's no red flag telling you what went wrong, just silence where trades should be.

The good news is that silent failures like this almost always come from a small set of causes, and they sit in a predictable order — terminal, account, VPS, source, app rules, billing. Rather than restarting MetaTrader and hoping, it's faster to work through each layer methodically. This article gives you that sequence, from the thirty-second check that fixes most cases to the less obvious ones further down the list.

Trading carries risk regardless of whether it's done manually or through automation, and a copier or EA that has stopped working silently is a reminder of that — losses on open positions don't pause just because new trades aren't copying. Whether you're running an EA directly, a Telegram-to-MT4/MT5 copier, or a mix of both, the diagnostic process is largely the same, because the underlying causes overlap: something at the terminal level, the account level, the infrastructure level, or the signal source has quietly stopped working without throwing an error you'd notice at a glance.

Start With the Terminal: Is AutoTrading Actually On?

Before anything else, look at the AutoTrading button in the MT4 or MT5 toolbar. It should be green. If it's turned red, automated trading is switched off at the terminal level, and no EA or copier attached to that terminal will place a single trade, regardless of how correctly it's configured underneath.

This happens more often than people expect. A Windows update, a VPS reboot, or MetaTrader restarting after a crash can all reset AutoTrading to its off state. If you've recently restarted your computer or VPS and trades stopped immediately afterwards, this is the first thing to rule out — it takes seconds to check and instantly explains an EA stopped copying trades with no other symptoms.

The second thing to glance at is the smiley face icon in the top-right corner of the chart the EA is attached to. A genuine smiley means the EA is loaded and AutoTrading is enabled for that chart. A neutral or frowning face means something is off — either AutoTrading is disabled globally, or the EA itself doesn't have permission to trade, which is the next layer to check.

Check the EA or Copier's Own Settings

AutoTrading can be on at the terminal level while the individual EA or copier instance is still blocked from trading. This is a separate setting attached to that specific chart, and it's easy to lose without noticing.

Right-click the chart, open the EA's Properties, and go to the Common tab. There you'll see a checkbox labelled "Allow live trading" (or "Allow algorithmic trading" on newer builds). If it's unticked, the EA runs, analyses the market, and produces signals internally — but never sends an order to the broker. Nothing crashes. Nothing errors. It just sits there.

This checkbox resets more easily than most traders realise. Common triggers include:

• Re-dragging the EA onto the chart after tweaking an input, which reloads it with default settings
• Restoring the terminal from a template or profile that predates the tick being enabled
• A VPS provider or hosting tool resetting the terminal to a saved snapshot
• Manually removing and re-adding the EA after a platform update

If AutoTrading is green at the terminal level but this box is unticked on the chart, you've found an expert advisor not trading despite everything looking correctly set up on the surface.

Confirm the MT4/MT5 Account Is Actually Connected

Assuming both of the above check out, the next question is whether the account itself is genuinely connected — not just logged in, but connected with trading permissions.

The classic version of this: a trader enters the investor (read-only) password instead of the trading password. The terminal will often still log in successfully, showing account details, balance, and open positions. But because the investor password only grants viewing rights, no order — manual or automated — will ever go through. There's no obvious error dialog warning you that you've used the wrong credential; the terminal simply behaves as though it's connected while quietly rejecting every trade request.

A wrong broker server field causes a similar effect. If the server name doesn't exactly match what the broker issued, the account will show as offline, or it will retry endlessly without ever fully connecting. Broker-side account locks or scheduled maintenance produce the same visible symptom: the account sits offline, and nothing copies until it reconnects.

The fix here is simple to check but easy to overlook: look at the account status in the terminal. It needs to read Online, not just logged in. If it's offline for any reason — wrong password type, wrong server, a locked account, or broker maintenance — no new trades will execute no matter how correctly the EA or copier is configured above it.

If You're on a VPS, Check the Session Itself

VPS setups introduce a failure mode that isn't visible from a casual glance, because the VPS can appear to be running perfectly well while the actual trading session inside it has stalled.

The most common version: the remote desktop session has frozen, disconnected, or timed out from inactivity, and the terminal window inside it auto-logged out or stopped receiving fresh price ticks. From the VPS provider's dashboard, everything looks fine — CPU usage normal, uptime counting, service marked as running. But the chart inside that session is showing candles from several hours earlier, meaning the terminal isn't actually processing anything live.

Things worth checking specifically on a VPS:

• Connect to the session directly (not just check the provider's status page) and confirm the price feed is moving in real time
• Check the terminal's connection indicator in the bottom-right corner for a live signal bar rather than a broken one
• Look at the terminal's Experts or Journal tab for a disconnection or re-login entry around the time trades stopped
• Confirm the VPS itself hasn't hit an idle timeout or auto-logout policy set by the provider

If the session shows stale prices while the provider dashboard says everything's healthy, this is almost certainly your cause. It's one of the more deceptive failure points because every surface-level indicator you'd normally trust — the VPS is up, the terminal is open — tells you everything's fine.

Check the Signal Source Itself

If the terminal, EA settings, account connection, and VPS session all check out, the problem may not be on the trading side at all. It may simply be that no new signals are arriving to copy in the first place.

For Telegram-based copying, the connection between your copier and Telegram can drop independently of anything happening in MetaTrader. Session expiry, a 2FA prompt that needs re-confirming, or losing access to a channel (removed, made private, or the invite revoked) will all sever that link silently. The copier side keeps running, the MT4/MT5 account stays online, but nothing new ever comes through because there's nothing left to copy.

The fix for a Telegram signal copier that's stopped working this way isn't in the EA or the terminal at all — it's reconnecting the Telegram source from the sources page in your copying tool. Restarting MetaTrader or re-checking AutoTrading won't touch this layer, because the terminal was never the problem.

This is also where checking a message-level log earns its keep. MarketSync's Logs/Live signals section shows whether a specific Telegram message was received, parsed, executed, skipped, or rejected, along with the specific reason. If a signal never even shows as received, that points straight at the Telegram connection rather than anything downstream in the terminal.

Check Whether the Copier's Own Rules Are Silently Blocking Trades

Once the terminal, account, and connection layers are confirmed working, there's still a layer that sits above all of them: the copier's own rules for when and whether to place a trade at all. These are deliberate settings, not faults, but they behave exactly like a fault when you've forgotten one is active.

Pause Toggles and Per-Source Pauses

Most copying tools have an account-level "Receiving signals" toggle and a "Pause copying" setting. If either is off or enabled respectively, the account stops copying entirely with nothing visible elsewhere in the interface to flag it — the account looks otherwise normal.

A subtler version of the same thing happens at the source level. A single Telegram source, or even one specific topic within a forum-style channel, can be paused on one account while every other source on that same account keeps copying normally. This makes the issue look like it's specific to that provider or channel, when actually it's a pause state sitting on your own account configuration.

Risk Rules That Block New Trades Without an Error

Risk controls such as max open trades, a daily loss limit, or a daily profit target exist to protect an account, but they block new trades the moment their condition is met, and they don't throw an error when they do.

Take a concrete case: max open trades is set to 5, and the account already has 5 positions open. A new signal arrives. It doesn't queue, wait, or retry — it's skipped outright. Even if one of the five open positions closes a minute later and frees up a slot, that skipped signal does not open retroactively. It's gone. The next signal that arrives after the slot frees up will copy as normal, but the one that arrived while the account was at capacity won't come back.

The same logic applies to daily loss limits and profit targets — once triggered, they stop new trades from copying for the rest of that period, silently, until the condition resets.

Symbol Mismatches and Missing Stop Loss

Two more technical mismatches cause skips rather than errors, and both are easy to miss because the account, connection, and rules all look fine otherwise.

The first is a symbol name mismatch. A signal might read "GOLD" while your broker's exact symbol for the same instrument is "XAUUSD.pro" or another suffixed variant. Unless symbol mapping is configured to tell the copier that these refer to the same instrument, the trade is skipped — the copier has no way to know they're equivalent on its own.

The second is a missing stop loss. If your account is set to require a stop loss on every trade and a signal arrives without one, it's skipped rather than copied, even if every other part of the signal is valid. Related to this: if the calculated lot size for a trade comes out below the broker's minimum tradable size, that trade is also skipped unless the account is set to fall back to the broker's minimum instead.

Rule Out a Billing or Platform-Wide Outage

Sometimes none of the above applies because the issue isn't in your setup at all — it's on the provider side.

If a subscription payment fails and the grace period that follows runs out, the account can enter a billing-suspended state. In that state, new trades stop copying and the dashboard becomes read-only, though positions that were already open continue to be managed rather than abandoned. This can look identical to a technical fault from the trader's side — no new trades, no visible error in the terminal — when the actual cause is a lapsed payment.

It's also worth checking whether the issue is wider than your account. A public status page showing the health of the platform's API, Telegram ingestion, and MT bridge components can help you check whether copying has stopped for everyone or just for you. MarketSync provides exactly this kind of status page, which is a faster way to rule out a provider-side outage than testing your own setup repeatedly.

The Full Checklist: What to Check When Your Trade Copier Stopped Working

Work through these in order rather than jumping around. Each one rules out an entire category before you move to the next:

1. AutoTrading button in MT4/MT5 — confirm it's green, not red
2. EA's "Allow live trading" setting in Properties → Common — confirm it's ticked
3. Account connection — confirm the account shows Online, and that you've used the trading password, not the investor password, with the correct broker server
4. VPS session status — connect directly and check prices are live, not stale
5. Telegram/source connection — confirm the source is still connected and hasn't hit a session expiry or 2FA prompt
6. Pause toggles and risk rules — check account-level and per-source pause states, plus max open trades, daily loss limit, and profit target settings
7. Symbol mapping and stop loss requirements — confirm the signal's symbol matches your broker's exact naming, and that any "require stop loss" setting isn't skipping unprotected signals
8. Billing status or provider status page — confirm your subscription is active and check for a platform-wide outage

If you're using a tool with a message-level log, checking that first can shortcut several of these steps at once — a message logged as "skipped: max open trades" or "unparsed" tells you exactly which layer to look at rather than working through the full list blind.

Frequently asked questions

Why did my EA stop trading after I restarted my computer or VPS?

Restarts frequently reset AutoTrading to off, or reset the EA's "Allow live trading" checkbox if the terminal reloads a template or default profile. Check both settings first, since a restart is one of the most common triggers for this specific silent failure.

Can a broker block automated trading during news events or maintenance?

Brokers control their own maintenance windows and any trading restrictions, and this sits outside what your EA or copier controls. If it happens, it would typically show up as your account going offline in the terminal rather than as a fault in the copier itself, so check account status first before assuming the copier is broken.

Why does my copier work on one MT4 account but not on another with the same settings?

Each MT4/MT5 account has its own connection status, its own attached sources, and its own pause and risk rule settings, even under the same subscription. A source being paused on one account, or a risk rule such as max open trades already being hit on one account and not the other, produces exactly this symptom — everything works on one account and not the other despite similar-looking configuration.

Will a trade that was skipped copy later once the blocking issue is fixed?

No. Signals skipped due to max open trades, a paused source, or a missing stop loss are skipped outright rather than held for later — they don't queue and won't execute retroactively once the blocking condition clears. Only signals that arrive after the issue is fixed will copy normally.

How can I tell if MetaTrader itself crashed versus the EA simply stopping?

If MetaTrader crashed, the terminal window won't be open at all, or you'll find a crash entry in Windows' event logs or the terminal's own log files. If the terminal is open and running but the EA stopped trading, you'll usually see a neutral or frowning smiley icon on the chart rather than any crash indicator.

Does closing the MetaTrader terminal window stop a trade copier from working?

Yes, if the terminal itself isn't running, nothing attached to it can place trades, regardless of how the EA or copier is configured. This is why automated setups are typically run on a VPS that stays on continuously, rather than a home computer that gets shut down or put to sleep.

Where to Look Next

If you've worked through the checklist and still can't find the cause, the fastest next step is a message-level log rather than more guessing in the terminal. Seeing whether a specific signal was received, parsed, executed, or skipped — and why — narrows the problem down immediately, rather than leaving you to test each layer in isolation. MarketSync's Logs and Live signals section is built for exactly this: checking what happened to a specific message rather than assuming where the fault lies.