New

11 tools. $557.98 if bought one by one. 5 new Premium desks inside.$557.98 one by one

$97 once$97See all 11See it
ProEA Lab · MT5, TradingView and trading research · Evidence standards
Systems

MT5 EA Not Taking Trades? Six Checks and the Codes That Name Them

EA attached but no trades? Check both Experts and Journal, then the EA's permissions, symbol and request results. An empty log cannot identify the cause. Codes such as 10027, 10018, 10014 and 10019 help narrow the next check.

PL · 4 min readUpdated
Explainer cover titled MT5 EA not taking trades: six checks, one log line. A row of six check boxes, Algo Trading button, EA's own permission, account allows EAs, symbol is trading, lot size is valid and free margin, with the first one crossed out and the Journal line retcode 10027: Autotrading disabled by client terminal.
When an MT5 EA takes no trades, check Toolbox → Experts and Journal. An empty log alone cannot identify the cause. Confirm the EA initialized and receives ticks, then check its permissions and request results. Codes 10027, 10018, 10014 and 10019 identify client-terminal automated trading, session, volume and margin issues respectively.
One order, six checks, one log line.Pick a case: where the order stops, and what the Journal says.
EA on XAUUSDsends: buy orderCHECK 1AlgoTradingbuttonTerminaltoolbarTERMINAL_TRADE_ALLOWED✕CHECK 2EA's ownpermissionEA properties →CommonMQL_TRADE_ALLOWEDCHECK 3Accountallows EAsYour broker'sserverACCOUNT_TRADE_EXPERTCHECK 4Symbol istradingSpecification →Sessionstrade sessionCHECK 5Lot size isvalidSpecification →Volumemin / max / stepCHECK 6Free margincovers itToolbox → Tradefree marginTOOLBOX → JOURNALfailed market buy 0.10 · retcode 10027: Autotrading disabled by client terminalThe toolbar's Algo Trading button was off. It blocks every EA in the terminal, evenone whose own permission is ticked.

A simulated, illustrative order: the symbol, lots and log layout are examples, not a recorded session. The codes and their wording are MQL5's.

Read as text
  1. The EA's entry rule fires: it sends a buy order (0.10 lots).
  2. It passes 0 of 6 checks, then stops at "Algo Trading button".
  3. failed market buy 0.10 · retcode 10027: Autotrading disabled by client terminal. The toolbar's Algo Trading button was off. It blocks every EA in the terminal, even one whose own permission is ticked.

How this window was chosen: The checks in order: the toolbar's Algo Trading button (TERMINAL_TRADE_ALLOWED), the EA's own permission (MQL_TRADE_ALLOWED), the account's permission for EAs (ACCOUNT_TRADE_EXPERT), then the symbol's session, lot size and free margin. Return codes and their wording from MQL5's trade server return codes, checked 2026-10-08: 10009 Request completed; 10014 Invalid volume in the request; 10018 Market is closed; 10019 There is not enough money to complete the request; 10026 Autotrading disabled by server; 10027 Autotrading disabled by client terminal.

Read the Journal first

Two logs matter, both in the Toolbox: Experts holds messages from running EAs and indicators, while Journal records platform and trade operations (MetaQuotes logging guide). Look in both; the visible tabs contain recent entries, and Open accesses saved logs for earlier dates. A missing line is not proof that the entry condition failed. The codes below are from MQL5's trade server return codes, checked 2026-10-08.

With source access, record initialization and tick processing, the entry decision, and any local permission or preflight exit. For a request, inspect the function's return value and the result fields: OrderCheck can stop the path before OrderSend, and OrderSend requires checking result.retcode; a true return does not by itself prove a fill. Capture GetLastError() when diagnosing a failed call. Without source access, ask the developer for these diagnostics rather than inferring them from silence. Logging and request-result guidance checked 2026-10-10.

CodeMQL5's wordingWhere to fix it
10027Autotrading disabled by client terminalToolbar → Algo Trading button
10026Autotrading disabled by serverYour broker: the account doesn't allow EAs
10017Trade is disabledSpecification → trade mode for the symbol
10018Market is closedSpecification → sessions; wait for the open
10014Invalid volume in the requestThe EA's lot input vs the symbol's min, max and step
10016Invalid stops in the requestStop-loss or take-profit, for example too close to price
10019There is not enough money to complete the requestLower the lot or risk input

Use itCopy the exact Journal line, with its time and symbol, before you change anything.

Watch outChanging three settings at once tells you nothing about which one was wrong.

The three permission switches

All three must be on (MQL5 trade permission, checked 2026-10-08):

  1. The Algo Trading button on the toolbar (TERMINAL_TRADE_ALLOWED). Off, it blocks every EA in the terminal (MetaQuotes).
  2. The EA's own permission: the EA's properties → Common → Allow Algo Trading, called Allow Auto Trading in older builds (MQL_TRADE_ALLOWED).
  3. The account: the broker can disable EAs (ACCOUNT_TRADE_EXPERT), and an investor (read-only) login can't trade at all (ACCOUNT_TRADE_ALLOWED).

Tools → Options → Expert Advisors can switch automated trading off on its own when you change account, profile, or a chart's symbol or period (MetaQuotes settings). If an EA stops after you switched something, look there.

The three checks the server makes

Permissions passed, the order still has to fit the symbol. In Market Watch, right-click it → Specification: the sessions, the minimum, maximum and step for lots, and the margin rules are your broker's (MetaQuotes). A lot of 0.005 on a symbol whose minimum is 0.01 returns 10014; an order on Saturday returns 10018.

Keep the exact message and request result. A code narrows the next check; a silent log leaves the cause unresolved.

If the install itself is in doubt, start from installing an EA on MT5. To see whether the entry rule fires at all, replay the period in the Strategy Tester.

Use this animation on your site.

Frequently asked questions

Why is my EA not taking trades in MT5?

Check Toolbox → Experts and Journal for initialization, runtime and trade-request messages. No trades can mean no entry signal, a local permission or preflight failure, or a rejected request. If a request result is available, 10027 means client-terminal automated trading is disabled, 10018 the market is closed, 10014 the volume is invalid, and 10019 there isn't enough margin.

What does error 10027 mean in MT5?

TRADE_RETCODE_CLIENT_DISABLES_AT, "Autotrading disabled by client terminal" in MQL5's list. Turn on the Algo Trading button on the toolbar. It blocks every EA in the terminal, even one whose own permission is ticked.

My EA has the Allow Algo Trading box ticked. Why won't it trade?

That box is one of three permissions. The toolbar's Algo Trading button must be on too, and the account must allow EAs (ACCOUNT_TRADE_EXPERT). An investor (read-only) login can't trade at all.

Why does my EA trade on demo but not on live?

The two accounts can have different symbol names, sessions, minimum lots and margin. Compare Market Watch → Specification for the symbol on both, and read the live Journal for the return code.

The Journal is empty. What does that mean?

An empty Journal alone does not prove that no order was attempted or that the entry rule failed. Check Experts too, then open the saved logs for the correct date and terminal. Confirm initialization, incoming ticks, symbol, timeframe and inputs. If you have source access, log the entry and preflight decisions and the request result; otherwise ask the EA developer for that diagnostic evidence.

Does MT5 stop my EA when I switch accounts?

It can. Tools → Options → Expert Advisors has "Disable automated trading when switching accounts", and the same for profiles and for changing a chart's symbol or period. With them ticked, re-enable Algo Trading after the switch.

Continue reading

Every Tick vs Real Ticks in MT5: Why the Same EA Gets Two Results

MT5's tester can feed your EA the broker's recorded ticks, ticks it generates from each minute's OHLC, or just the four OHLC prices. When a stop and a target sit inside one minute, those modes can disagree on which one filled.

Oct 8 · ProEA Lab

Explainer cover titled Every tick vs real ticks: one minute, two results. A single 1-minute bull bar with a long trade's stop-loss at 2,398.00 and take-profit at 2,402.50 inside it, and the generated tick path going open, low, high, close, stopping out at the low before it reaches the target.

Walk-Forward Testing: Steps, Example and Limits

Optimize on earlier data, freeze the rules, test on the next unseen period and repeat. A dated walk-forward example, efficiency pitfalls and MT5 forward-test limits.

Aug 10 · ProEA Lab

A brass stencil sliding along a long paper chart strip, exposing only one unmarked section at a time while the rest stays covered — poster titled Judge the Unseen Part.

How to Backtest an EA in MT5 (Strategy Tester, Step by Step)

Set up MT5 Strategy Tester, choose a modelling mode for your EA, and check execution delays, forward testing and profit-in-pips limitations. Read the report with its data and cost assumptions attached.

Jul 14 · ProEA Lab

A brass model aeroplane inside a glass wind-tunnel chamber on a dark laboratory bench, smoke lines streaming over its wings — poster titled Test Before Trust.