Incident Log — XAUUSD EA Sudden Failure
Symptoms
- ›EA runs but gets cancelled orders
- ›Unusual "trade context busy" errors in Journal
- ›EA appears active but no trades open for days
- ›New "expert advisor not permitted" type errors
How to confirm
Contact broker support. Ask specifically: "Has there been any change to EA or scalping trading policy?" Also compare your live account trade history with a demo account on the same broker — if demo trades normally and live does not, the restriction is account-level.
Resolution
Switch to a broker with an explicit ECN/STP EA-friendly policy. Attempting to work around policy restrictions is not advisable and risks account suspension.
Time to resolve
Days to weeks (broker migration takes time)
Safe to resume when
Only after confirming new broker has no scalping restrictions
Symptoms
- ›EA smiley face missing from chart
- ›Errors in the Experts tab referencing unknown functions
- ›"DLL not allowed" or similar system errors
- ›EA attaches but immediately removes itself
How to confirm
Check the MT5 build number (Help → About). Ask the EA developer which build they compiled against. If there is a mismatch, recompilation may be needed. Check the Experts tab for specific error messages — these usually identify which function or dependency failed.
Resolution
Contact the EA developer with the specific error messages. They will need to recompile against the current MT5 build. If you have source code access, recompile in MetaEditor yourself.
Time to resolve
Hours to days (depends on developer response time)
Safe to resume when
After developer provides updated .ex5 file compiled against current MT5 build
Symptoms
- ›Single very large losing trade visible in history
- ›Stop loss triggered far from the set level (slippage)
- ›Loss occurred at a timestamp matching a news event
- ›Account in significant drawdown after one event
How to confirm
Cross-reference the losing trade's timestamp in the account history with the economic calendar (Forex Factory, Investing.com). If the trade opened or closed within 5 minutes of an NFP, CPI, FOMC decision, or similar high-impact event, this confirms the cause.
Resolution
Review whether the EA has a news filter parameter. If yes, check it was activated. If no news filter exists, contact developer about adding one, or manually disable the EA 30 minutes before and after high-impact events.
Time to resolve
Immediate diagnosis — the event is already done. Review news filter settings before next event.
Safe to resume when
After confirming news filter is active for next high-impact event window
Symptoms
- ›EA offline notification or VPS provider alert
- ›Position open but no EA management occurring
- ›Last Journal entry timestamp significantly in the past
- ›Unusual open P&L on unmanaged position
How to confirm
Check your VPS provider's status page for reported outages. Compare the last Journal entry timestamp to when EA management of the open trade stopped. If there is a gap, the VPS was down during that period.
Resolution
If positions are still open: access account through broker mobile app or web platform immediately. Assess risk manually. Once VPS restored: check all positions, ensure EA has reconnected, review any unmanaged period in trade history.
Time to resolve
VPS restoration: minutes to hours. Account damage: depends on price movement during outage.
Safe to resume when
After VPS uptime monitoring is in place and broker-level hard stop losses are confirmed on all positions
Symptoms
- ›EA shows smiley face but opens zero new trades
- ›No Journal errors
- ›This persists across multiple sessions
- ›Spread on XAUUSD chart visibly elevated vs previous weeks
How to confirm
Open your XAUUSD chart during London open (08:00–09:00 GMT). Check the current bid-ask spread. Compare to the EA's SpreadFilter parameter (usually visible in EA settings). If current spread > SpreadFilter, the EA is correctly blocking all trades.
Resolution
Option 1: Switch to a broker with tighter gold spreads. Option 2: Adjust the SpreadFilter parameter higher — but understand this accepts worse execution costs and may reduce profitability.
Time to resolve
Immediate (once diagnosis confirmed)
Safe to resume when
After either broker change or SpreadFilter adjustment with awareness of changed risk profile
Why Some EAs Fail on XAUUSD Suddenly:
Diagnosing Abrupt Failure
Published 26 June 2026 · 12 min read
Abrupt EA failure — where performance drops immediately rather than gradually — has five primary causes: broker policy change restricting EA trading, an MT5 platform update breaking EA compatibility, a news event causing catastrophic slippage on a single trade, VPS outage leaving positions unmanaged, or a permanently widened spread exceeding the EA's spread filter threshold. Each has distinct symptoms and a specific MT5 diagnostic. The widget below guides you to the most likely cause in under a minute.
Sudden Failure vs Gradual Degradation
The distinction matters because it changes the diagnostic process entirely. Gradual degradation — where an EA that worked for 3 months starts producing smaller wins, then breaks even weeks, then losing weeks — is almost always a market regime issue or broker spread creep. It happens over time, and the signal-to-noise ratio is low enough that many traders do not notice until significant damage is done.
Sudden failure is different: the EA was producing normal results last Tuesday, and on Wednesday it either produced a catastrophic loss or simply stopped doing anything at all. The abruptness is the diagnostic signal. Something external changed — not the market in general, but a specific operational condition that the EA depends on to function correctly.
The five incident types above cover the space of sudden failures. When your EA fails abruptly, run through the diagnostic tool below before concluding the EA itself is broken. In the majority of sudden failure cases, the EA code is fine — something in the operational environment changed.
The Spread Filter Edge Case — Goldie Razor Example
Incident Type 5 is the most commonly misidentified sudden failure — and the one traders most frequently panic about unnecessarily. The EA appears dead: smiley face present, no Journal errors, no trades. It looks like the system has stopped working. But the SpreadFilter parameter is simply doing its job.
Goldie Razor V2.8.4 includes a default SpreadFilter of 18 pips. During holiday weeks — Christmas, Easter, Lunar New Year — gold spreads at many brokers widen to 25–40 pips as liquidity thins. The EA correctly detects that the entry cost exceeds its acceptable threshold and refuses to trade. This is not a failure. It is the spread filter protecting you from entries where the spread alone would consume most or all of the expected profit.
The diagnostic: at London open (08:00–09:00 GMT), check the current spread displayed on your XAUUSD chart. If it reads 22 pips and the SpreadFilter is set to 18, the silence is intentional. Wait for normal spread conditions to return — typically within 24–48 hours after a holiday period ends.
Diagnose Your Sudden Failure
Answer 5 branching questions. The tool uses your answers to identify the most likely incident type.
Is the EA still showing on the chart with a smiley face (not an X)?
First Response Protocol: What to Check Immediately
When you notice your EA has suddenly stopped performing, the immediate priority is to assess open position risk before diagnosing the cause. If there are open trades, check their current P&L in your broker account — you can do this through the broker's web platform or mobile app without needing MT5 running. If open trades are in significant unrealised loss and the EA is offline, you may need to close manually to limit damage.
Once open position risk is managed, open MT5 and check in this order: (1) Is the EA smiley face present on the chart? (2) What is the most recent message in the Experts tab? (3) What is the most recent message in the Journal tab? (4) What is the current spread on XAUUSD? (5) What does the recent trade history show — any unusual timestamps, large losses, or cancellations?
These five checks take under two minutes and give you the raw data to identify the incident type. Run through the diagnostic widget above once you have this information.
Related Reading
Why do most gold trading EAs fail?
The statistical context — sudden vs. gradual failure and where each fits in the overall picture.
Creating a backup plan when your EA fails
The full contingency protocol for any type of sudden EA failure.
What happens to my EA if the broker goes down?
Incident Type 4 in depth — broker-side outages and position management.
Why did my EA fail during the jobs report?
Incident Type 3 specifically — NFP and major news events in detail.
Is my XAUUSD EA being blocked by my broker?
Diagnosing Incident Type 1 — broker restriction and policy changes.
Frequently Asked Questions
Start by contacting support directly and asking: "Has there been any change to your scalping or EA trading policy in the last 30 days?" Some brokers will confirm changes; others will not. Separately, review your trade history for the period before and after performance dropped — look for an increase in "trade context busy" errors, cancelled orders without execution, or unusual Journal entries. If your EA trades normally on a demo account at the same broker but not on live, this is a strong indicator of live-account-specific restrictions being applied.
Yes, though it is relatively uncommon. MT5 updates occasionally change the way specific MQL5 functions behave, deprecated functions stop working, or the EA was compiled against an older build that is no longer fully compatible. The symptom is usually an error in the Experts tab rather than a smiley face disappearing — the EA attaches but generates runtime errors when it tries to execute. Recompiling the EA source code against the new MT5 build often resolves compatibility issues, but this requires access to the source code (.mq5 file) and the MetaEditor application.
Stop losses are guaranteed to close your position, but not at the exact price set. During a major news event (NFP, FOMC rate decision, CPI), gold can gap 50–200 pips in a fraction of a second. Your broker's server may be overwhelmed with orders. The stop loss triggers at the next available price — which could be far beyond the set level. This is called "slippage" in normal conditions and "gapping" in extreme ones. It is not your broker failing — it is the market itself lacking the liquidity to fill your order at the intended price. The protection is to not have open trades during major news events, which is what most EA news filters are designed to address.
First priority: log into your broker account directly (via browser or mobile app, not MT5) and assess whether any positions are still open. If yes, and if they are in significant loss, you face a decision: close manually at current price, or leave them and hope for recovery. The EA cannot make this decision for you — it is offline. Once the VPS is back and the EA reconnects, it will manage open positions according to its logic, but the period of unmanaged exposure is already done. After resolving the immediate situation: get an uptime monitoring alert on your VPS so you are notified within minutes of any future outage.
Most scalping EAs have a SpreadFilter parameter — a pip value above which the EA will not open new trades. If your broker permanently increases its typical gold spread above this threshold — for example, from an average of 12 pips to an average of 22 pips — the EA will stop opening trades entirely. It looks like the EA has stopped working. No trades, no Journal errors, the smiley face is present — just silence. The diagnosis is simple: check the current spread on your XAUUSD chart at London open and compare to the EA's SpreadFilter parameter. If current spread > SpreadFilter, trades are blocked by design.
Goldie Razor V2.8.4
M15 breakout + H4 EMA filter — built for XAUUSD on MT5