Why Do My Gold Trading EAs
Suddenly Stop Working?

Why Gold EAs Stop Working: The 4 Root Causes

Most EA traders, when their gold expert advisor stops producing trades, assume the EA itself is broken or the strategy has stopped working. In practice, the EA logic is rarely the culprit in a sudden stop. The four causes above are all operational — they involve the technical environment the EA runs in, not the EA's internal strategy code.

The distinction between operational failure and strategy failure matters enormously. An operational failure — VPS down, broker restriction, parameter corruption — can be diagnosed and fixed in minutes. A genuine strategy failure — where the EA's entry logic stops generating alpha on the current market — takes weeks to confirm because you need enough trades to distinguish bad luck from systematic underperformance. Treating an operational issue as a strategy failure means you may abandon a working EA unnecessarily. Treating a strategy failure as an operational issue means you keep running an EA that is genuinely not working.

The hierarchy of diagnosis is: confirm the EA is technically running first, then confirm the trading environment (broker, VPS, platform) is functioning correctly, then and only then assess whether the strategy itself needs review. This page walks you through that hierarchy, starting with the fastest checks and progressing to the slower ones.

For the broader picture of external causes behind sudden EA failures on XAUUSD — including broker policy shifts, MT5 update compatibility breaks, and news event catastrophe — those are addressed separately. This page focuses specifically on the user-facing experience: your EA was working yesterday and stopped today.

How to Read Your MT5 Journal to Diagnose EA Failure

The MT5 Journal is the most important diagnostic tool available to EA traders and is systematically underused. Most traders look at their account balance and open positions but never open the Journal — which is where every significant EA event is logged with a timestamp.

To access it: in MetaTrader 5, go to View in the top menu, then Terminal, then click the Journal tab in the terminal panel at the bottom of the screen. The Journal shows every significant system event: EA loads, EA removes, connection events, order attempts, order confirmations, order errors, and system messages from MT5 itself.

The most effective diagnostic approach is to scroll to the timestamp when the EA last placed a trade and look for what happened immediately after. Did a connection warning appear? Did an error code appear in the Experts tab? Did the EA remove itself? The answer to one of these three questions will point to the cause in most cases.

The Experts tab (a separate tab in the same Terminal panel) shows output from the EA's own internal logging. Well-built gold EAs write diagnostic information here — including when signals are generated but blocked by filters, current spread vs filter threshold, and active trade management events. If your EA writes to the Experts tab, this is the first place to look — it provides richer diagnostic information than the general Journal.

MT5 Error Codes That Mean Your EA Is Broken (Not Just Quiet)

When the EA is genuinely broken rather than just waiting, specific error codes appear in the Experts tab or Journal. Here are the most important ones for gold EA traders:

Error codes 4xxx are MQL5 runtime errors from the EA's own code. Error codes 10xxx are trade server return codes from the broker. A combination of both types in the same session often indicates a misconfigured parameter (4051) triggering a series of rejected orders (10006) — which looks like a broker restriction but is actually a configuration problem.

Is My EA Stopped or Just Waiting? How to Tell the Difference

This is the most common question from EA traders experiencing a quiet period. The EA is running — you can see the smiley face — but no trades have been placed in 24, 48, or even 72 hours. Is this normal? Is the EA broken? Is this a regime change?

The definitive test: open the Experts tab and look for the most recent entry. If the EA is writing something there — even if it is just logging "no signals" or "spread above filter" — the EA is alive and processing ticks. If the most recent entry in the Experts tab was several hours or days ago, the EA has either stopped receiving tick data (VPS/connection issue) or was quietly removed from the chart without your knowledge.

A gold EA operating in a regime shift will typically still log tick processing but record zero signal attempts. This is the key fingerprint of cause C4: the EA is running correctly, the market is moving, but the EA's entry conditions — which might require a specific combination of session time, spread level, trend direction, and momentum threshold — are not being met simultaneously.

If you are uncertain about whether a quiet period is a regime issue or a technical failure, reviewing when to take a temporary pause while investigating provides the framework for making this call without either over-reacting (disabling a healthy EA) or under-reacting (ignoring a genuine failure).

The 5-Minute EA Triage Protocol Every Gold Trader Needs

Run this protocol every time your gold EA goes quiet for more than 24 hours without an obvious explanation:

1. 01

   Confirm the EA is attached (30 seconds)

   Open MT5. Find the XAUUSD chart your EA runs on. Look for the smiley face icon in the top-right corner of the chart. If it is there, proceed. If it is an X, the EA is disabled — right-click the chart, select Expert Properties, ensure AutoTrading is enabled, and click OK.

2. 02

   Check the Experts tab (60 seconds)

   View → Terminal → Experts tab. Read the most recent 10 entries. Look for any error messages, especially codes containing numbers (129, 138, 4051, 10006). Note the timestamp of the most recent entry — if it is older than 30 minutes during a trading session, the EA may have stopped receiving ticks.

3. 03

   Check the Journal tab (60 seconds)

   View → Terminal → Journal tab. Scroll to the timestamp of the last known trade. Look for any connection events, disconnect messages, or EA-related warnings in the window immediately after that last trade.

4. 04

   Check current spread vs SpreadFilter (30 seconds)

   On the XAUUSD chart, look at the current bid-ask spread (displayed in the chart header or market watch). Compare it to the EA's SpreadFilter parameter in Expert Properties. If current spread is above SpreadFilter, the EA is correctly blocking trades — not broken.

5. 05

   Place a manual test on demo (90 seconds)

   On a demo account at the same broker, try placing a manual XAUUSD trade at the current price. If the order goes through normally, the broker's XAUUSD execution is functioning. If the order is rejected, you have found your answer — broker-side restriction or execution issue.

Total time: under 5 minutes. At the end, you will have either identified the cause or confirmed the EA is technically healthy (pointing to regime C4 as the explanation). If you have open positions and the EA is genuinely offline, the 5-minute triage can wait until after you have checked and secured your position — position safety always comes first. More detail on broker-side outages as a failure cause and what to do with open positions in that scenario.

When to Contact Your EA Developer and What to Tell Them

Not every EA issue requires developer involvement. Contact the developer when: (1) the Experts tab shows a specific error referencing an internal function name or line number — this indicates a code-level issue rather than a configuration problem; (2) the EA fails after an MT5 update and recompilation in MetaEditor does not resolve it; (3) you have confirmed through the 5-minute triage that the broker execution is normal, the settings are correct, and the EA is receiving ticks — but it still generates no trades over two complete London sessions.

When you contact your developer, include: the exact error messages from the Experts tab (copy and paste them, with timestamps); your MT5 build number (Help → About); the account type (live or demo, ECN or Standard); the broker name; and the last date when the EA traded normally. This information allows the developer to reproduce the issue without spending time on diagnostic questions you can answer upfront.

Deciding whether to restart or shut down while waiting for a developer response depends on whether you have open positions and your assessment of the current risk environment. The safest default while awaiting developer response: disable the EA (right-click → Disable Expert, not Remove) so it stops attempting new trades but remains attached for diagnostic purposes.

How to Prevent Sudden EA Failures With Proactive Monitoring

The best time to set up failure detection is before the failure happens. Three layers of monitoring eliminate most of the damage from sudden EA failures:

A complete guide to setting up an early warning system before EAs fail walks through each of these monitoring layers in detail, including specific free and paid tools for 24/7 EA monitoring without manual checking.

Finally, understanding the full spectrum of automated trading risks and safeguards for XAUUSD provides the broader context for why monitoring matters and what else can be done to protect an automated trading operation from unexpected failures.

Frequently Asked Questions

Related Articles