EA Not Trading in MT5? How to Separate a Blocked Setup from Normal Waiting
You attach an EA to a chart, leave the terminal running, and come back to find no trades. Should you wait, change the settings, or contact the developer?
No trades is an observation, not a diagnosis. First separate three possibilities: trading is blocked, the EA has documented reasons to wait, or there is not enough information to tell. This guide walks through that distinction using MT5's documented controls and logs.
1. Check the terminal and the intended chart
Record the EA name and version, chart symbol, timeframe, and the time of the problem. Confirm that you are looking at the terminal where the EA is actually meant to run. A local terminal and a virtual terminal are different places to investigate.
Check the connection indicator and the latest quote time. In Market Watch, open the symbol's Specification and inspect its trading mode and trading sessions. The broker's complete symbol name matters: do not assume that two similar names refer to the same instrument. Quotes being visible does not, by itself, establish permission to trade. [1][2]
Trading sessions follow the broker's server schedule. MT5's desktop Journal displays event times in the computer's time zone. Record both time references before comparing them. [2][3]
2. Check both automated-trading permissions
MT5 provides a platform-wide permission and a permission for each EA. The toolbar control, often labelled Algo Trading, corresponds to the platform-wide control described as Allow Auto Trading in the official help. When that control is off, an EA can continue running calculations while being unable to trade. An individual EA can also be prohibited from trading. [1][4]
| Check | Where to look | What it establishes |
|---|---|---|
| Platform permission | Toolbar; Tools → Options → Expert Advisors | Whether automated trading is allowed across the terminal |
| Individual EA permission | Running EA in Navigator; its properties when appropriate | Whether that EA is allowed to trade |
| Account permission | Account access and relevant Journal messages | Whether the account permits trading; investor access is read only |
MT5 also has options that disable automated trading after an account, profile, symbol, or timeframe change. Check whether one of those changes preceded the problem. A disabled permission explains a restriction; it does not prove that an entry signal occurred. [1][4]
Record the state before changing it. Do not enable every permission, increase risk, or remove filters merely to make an order appear. Opening an EA's properties is not completely passive: MT5 documents that execution waits while that dialog is open. Prefer the visible Navigator state for an initial check. [1]
3. Read Experts and Journal together
In Toolbox, inspect the same time window in both tabs:
- Experts records EA and indicator activity, including their messages and alerts.
- Journal records terminal events, including connection and trading operations.
Look for initialization failures, disconnections, and order-processing messages. The tabs show recent entries; their context menu's Open or Viewer command provides access to older logs. [3]
An empty log interval is not proof that the EA checked its conditions and decided to wait. Some EAs do not log every decision. If you are using MetaTrader's virtual hosting, inspect the virtual terminal's journal as well; a local log alone does not describe the remote run. [5]
Official log example: the Journal screenshot in [3] shows a Network entry containing terminal synchronized . It reports terminal synchronization, not a check of the EA's entry conditions. This is an older official screen example, not a log captured from our trading account.
4. Read the result of an attempted order
If the EA exposes a trade result, record the exact code and surrounding message. The official MQL5 reference defines these examples: [6]
| Code | Meaning | Next check |
|---|---|---|
| 10017 | Trading disabled | Account and symbol trading restrictions |
| 10018 | Market closed | The symbol's trading session and server time |
| 10021 | No quote available to process the request | Connection and quotes for that symbol |
| 10026 | Automated trading disabled by the server | Broker/account restriction |
| 10027 | Automated trading disabled by the client terminal | Terminal and EA trading permissions |
These are documented code examples, not logs collected from a test or live account. Your EA may display a description rather than a number. Preserve its actual wording.
A code concerns an attempted trade operation; it does not explain every reason an EA might never attempt an order. A client-side prohibition also does not prove that the request reached the broker. No code is not the same as no problem.
5. Decide what the evidence supports
Consider three diagnostic examples. They illustrate the method; they are not observed trading results.
| Evidence available | Supported conclusion |
|---|---|
| An order attempt is recorded with 10027 | A client-side automated-trading restriction needs investigation |
| The EA is running, required data is current, and its diagnostic explicitly says a documented entry condition is false | Waiting for that condition is supported for that moment |
| No position and no useful diagnostic message | The cause remains undetermined |
Waiting is a conclusion to support with evidence. Check the EA's documented requirements and, where available, the values it evaluated at the relevant time. Trading hours, spread limits, news filters, position limits, and new-bar rules are possible checks only if that particular EA actually uses them.
If the reason is still unclear, send the developer a focused record: EA version, MT5 build, full symbol name, timeframe, timestamp and time zone, relevant settings, and the surrounding Experts/Journal lines. Remove account numbers, credentials, and unrelated trading details before sharing. Ask: “Was an order attempted? If not, which condition prevented it?”
That answer determines the next step: resolve an identified restriction, wait for a documented condition, or obtain the missing diagnostic information.
Official sources
Checked on 18 November 2026. English control names are retained so they can be matched to the official documentation; labels can differ with platform language and build.
- MT5 Help — Expert Advisors and Custom Indicators; includes official settings screenshots
- MT5 Help — Market Watch and symbol specifications
- MT5 Help — Platform Logs; includes the official Experts/Journal screen example
- MQL5 Reference — Trade Permission
- MetaQuotes — How to migrate an automated trading environment to virtual hosting
- MQL5 Reference — Trade Server Return Codes
Prepared with AI assistance and checked against the official sources above. This is a general troubleshooting guide, not verification of any particular EA or evidence of trading performance.


