What Do I Need to Know Before Using a Gold EA?The 7-Item Pre-Launch Checklist

Why Pre-Launch Knowledge Prevents Most EA Failures

When an EA trader reports that their EA "stopped working" or "blew up the account," the root cause is almost always traceable to one of the seven knowledge items — not to the EA's strategy quality. Wrong broker (market maker spreads wiping out EA edge), no VPS (EA stopped during London session when PC went to sleep), wrong session window timezone (EA trading at 4 AM UTC instead of 9 AM UTC), no daily loss limit (one bad day became 30% drawdown), unknown drawdown expectations (EA closed at 12% drawdown that would have recovered to 5% by month end).

The EA is not the variable in these failure scenarios — the operational setup is. What to check before BUYING a gold EA (the due diligence guide before purchase) is in our pre-purchase guide. This page covers what to KNOW before USING the EA after purchase.

Item 1 — Strategy Logic: The Minimum Understanding

You do not need to read MQL5 code to understand your EA. You need to be able to answer five specific questions from the documentation or developer: What is the entry signal type (breakout, trend-following, mean-reversion)? What exits the trade (fixed take profit, trailing stop, time-based close)? What session does it trade (London, NY, both, or 24/5)? What happens on a losing streak (same lot size maintained, or any adjustment)? What market conditions cause its worst drawdowns?

If you can answer these five questions, you can diagnose performance issues. "The EA has had 8 losses in a row during a ranging XAUUSD week — this is its known weak condition, I will hold through it." This is only possible if you knew in advance that ranging conditions are the EA's weakness. Without this knowledge, 8 losses in a row feels like breakdown rather than expected behaviour.

Item 2 — Broker Requirements: The 7 Red Flags

Seven broker characteristics can systematically undermine EA performance regardless of strategy quality:

Item 3 — VPS Setup: What You Need and Why

A VPS (Virtual Private Server) is a cloud-based Windows computer that runs 24 hours a day, 7 days a week. MT5 and your EA run on this VPS continuously. When you turn off your local computer, the EA on the VPS continues trading completely unaffected.

The latency factor: a VPS in a London or New York datacenter can achieve 1–5ms latency to major forex brokers' servers in the same city. A home internet connection in Sydney, Singapore, or Mumbai typically has 100–300ms latency to the same servers. For scalping EAs that rely on fast order execution, this 20–60x latency improvement is directly relevant to execution quality.

VPS setup steps: (1) Choose a provider (Vultr, Contabo, or Windows VPS from your broker if offered), (2) Select Windows Server 2016 or later, 2GB RAM minimum, London or NY datacenter, (3) Connect via Remote Desktop (RDP), (4) Download and install MT5 on the VPS, (5) Log into your broker account on the VPS MT5, (6) Copy your EA file to the Experts folder, (7) Attach EA to XAUUSD chart and configure parameters. How to monitor your EA remotely once deployed is in our remote monitoring guide.

Item 4 — Risk Settings: The Lot Size Calculation

The 1% risk per trade rule is the starting point for XAUUSD EA risk management. At 1% risk per trade with a 20-pip stop loss:

Always set the daily loss limit parameter at 3–5% of account. This auto-stops the EA if the day has been unusually bad — preventing one bad session from compounding into a severe drawdown.

Item 5 — Session Windows: Timezone Offset Configuration

The timezone offset is the most technically specific knowledge item, but also one of the most consequential. Your EA has session window parameters: "Trade from Hour X to Hour Y." These hours are in your broker's server time, not UTC, not your local time.

Most MT5 brokers use UTC+2 in winter and UTC+3 in summer (EET/EEST, Eastern European Time). To trade the London open (07:00 UTC) with a UTC+2 broker: set session start to 09:00 in EA parameters (07:00 UTC + 2 = 09:00 broker time). To trade NY open (13:30 UTC) with a UTC+3 broker: set session start to 16:30 (13:30 UTC + 3 = 16:30 broker time).

Verification method: after the first week of live operation, review trade open times in MT5 history. All trade opens should fall within your intended session window in UTC. If they do not, recalculate the broker server time offset and adjust.

Items 6 and 7 — Drawdown and Monitoring: The Psychological Preparation

Drawdown is the part of EA trading that requires genuine pre-launch psychological preparation. Every EA will have drawdown periods. The question is whether you know what "normal" drawdown looks like for your specific EA.

If the EA documentation shows a historical maximum drawdown of 18% with an average recovery period of 3 weeks, and your account is currently at 15% drawdown in week 2 — you should hold. If you did not know the historical maximum drawdown was 18%, a 15% drawdown will feel like the EA has catastrophically failed. Whether you should use recovery mode on your gold EA (an advanced configuration decision related to managing drawdown) is in our recovery mode guide.

The monitoring protocol is simple but requires consistency. Daily check takes 5 minutes: confirm AutoTrading is enabled, note any trades since last check, verify account balance matches expectation. Weekly review takes 10 minutes: compare profit factor against expected range, check drawdown level against historical maximum, count trade frequency against expected average. Monthly: compare live performance to demo period benchmarks. The escalation rule: contact the developer if live performance is more than 30% below demo performance after 60 days. Continue without contact if performance is within 25% — this is normal live/demo variance.

The Demo Requirement: Why 30 Days Is Not Optional

The 30-day demo period is mandatory for four reasons that compound each other. First, it lets you verify the EA runs correctly on your specific broker and VPS combination before real money is involved. Second, it builds psychological familiarity with the EA's normal behavior: typical losing streaks, typical recovery patterns, typical inactive periods. Third, it reveals configuration errors — wrong session windows, wrong lot size, incorrect parameters — in an environment where the errors cost nothing.

Fourth, and most importantly, it establishes a benchmark. When you go live at minimum lot sizes, you can compare live performance to your 30-day demo benchmark. A close match (within 20–25%) confirms the EA is operating correctly in live conditions. A significant divergence (30%+ gap) signals that something in the live setup differs from demo — and you have the demo data to diagnose it against.