MT5 EA not trading? A systematic troubleshooting guide

What should I check first when an MT5 EA is not trading?

Check the problem in this order: terminal connection and account access, the main Algo Trading switch, the EA's individual trading permission, the EA and chart state, symbol and account compatibility, available margin, then the Experts and Journal logs. Keep the original preset while diagnosing. Increasing the lot size, removing risk limits, or changing many inputs at once does not reveal the cause and can create a different problem.

1. Confirm that MetaTrader 5 is receiving live quotes and is logged in with trading rights.
2. Confirm that automated trading is allowed both for the platform and for this EA.
3. Confirm that the intended EA is attached to the correct chart, symbol, and timeframe.
4. Check the broker's symbol specification, trading session, minimum volume, stop distance, account mode, and margin.
5. Read the newest Experts and Journal entries at the time a trade should have been considered.
6. Reproduce the same setup in the Strategy Tester or a demo account to separate EA logic from live account conditions.

This sequence separates a disabled terminal from a rejected order and both from an EA that is running correctly but has no valid entry. If you are setting up a YoForex product, compare each check with the current YoForex EA installation documentation rather than relying on a screenshot from a different version.

1. Confirm that the terminal can trade

A moving chart does not by itself prove that the account can submit an order. Verify that the terminal shows an active connection, current Bid and Ask prices are changing, and the selected trading account and server are the ones you intended to use. If quotes are frozen, resolve the connection or symbol subscription first. Restarting an EA cannot compensate for a disconnected terminal.

Check how the account was authorized. MetaTrader distinguishes full account access from investor access. According to the official MetaTrader 5 account connection documentation, investor authorization permits viewing and analysis but does not permit trading. Log in with the appropriate trading credentials through the broker's correct server. Never send an account password to YoForex support or paste it into a public message.

Next inspect the Algo Trading control in the toolbar and the Expert Advisors section of the platform options. The platform-wide permission can block every EA even when one EA's properties allow trading. MetaTrader can also be configured to disable automated trading after an account, profile, chart symbol, or timeframe change. A recent switch can therefore explain why an EA that worked earlier is now observing the market without submitting orders.

2. Verify the EA and chart state

Open the Navigator, find the exact EA name, and attach it to the intended chart. In the EA properties, confirm that automated trading is allowed for that application. After a successful start, the EA name and its enabled status should appear on the chart. MetaTrader's official guide to running Expert Advisors also notes that only one EA runs on a chart; attaching another replaces the first. Use separate charts when two EAs must run at the same time.

Match the symbol and timeframe required by the product documentation. Brokers may label the same market differently, such as adding a suffix or using a separate cash and futures symbol. A preset made for one symbol is not automatically compatible with another symbol that merely looks similar. If the EA reads the current chart, attaching it to an unintended symbol or timeframe can change its inputs, price scale, tick flow, or entry logic.

Check that the EA file and preset belong to the same documented version. When loading a saved preset, review the visible input values before accepting them. Do not assume a file with a familiar name contains the current configuration. The Private EA version comparison exists because versions can have different behavior and requirements; settings should not be moved between versions unless the documentation explicitly supports that use.

3. Check account and symbol constraints

The broker controls the account's trading permissions and the contract specification. Right-click the symbol in Market Watch and open its specification. The official MetaTrader Market Watch reference describes fields including spread, digits, volume limits, stop levels, and contract details. Compare those values with the EA's requested order rather than assuming that every broker uses the same limits.

MT5 supports both netting and hedging accounts, and the broker determines which system an account uses. The MetaTrader position-accounting reference explains that netting combines a symbol's exposure into one position, while hedging can keep separate positions, including opposite positions. This distinction can materially affect a basket or hedging EA. Read the documented account requirement for Private EA or Dynamic Hedger EA before running either product.

4. Decide whether there is an error or simply no valid entry

An EA can be loaded, enabled, and healthy without opening a trade. Automated software follows its programmed conditions; it does not need to produce an order every hour or every day. A time filter, spread limit, volatility condition, trend filter, maximum-position rule, cooldown, or an existing basket can make waiting the correct behavior. Product documentation should identify the relevant controls, but it cannot predict when the market will satisfy every condition.

Confirm that the symbol's trading session is open and prices are current. A chart may display historical bars when the instrument is closed. Wider spreads around rollover, market openings, or exceptional conditions may also exceed an EA's allowed spread. Do not remove the filter simply to force an entry. Record the broker server time, local time, symbol, Bid and Ask, and active session so that the observation can be compared with the EA's rules.

Also inspect existing positions and pending orders. The EA may enforce a maximum number of trades, manage only orders with a particular identifier, wait for a basket to close, or refuse a second position. Read the input labels and current product manual. The YoForex AI user manual explains the broader workflow, while the EA setup documentation covers platform-specific use.

5. Review inputs, risk controls, and available margin

Save a screenshot or preset of the current inputs before changing anything. Check for a zero or invalid lot value, a risk percentage that calculates below the broker's minimum volume, disabled trade direction, restrictive trading hours, a daily limit that has already been reached, a maximum-spread setting, or a maximum-position rule. A protective control can be the reason no order is sent, so classify the setting before deciding it is wrong.

Check equity, free margin, open exposure, and the broker's margin requirement. A platform may reject an otherwise valid request when the account lacks sufficient free margin. Reducing unrelated safeguards or depositing funds solely to make an EA trade is not a troubleshooting test. Use a demo account with representative settings to determine whether the request format and logic work without adding financial risk.

Change one variable at a time and note the result. If ten inputs change together, a later trade does not establish which change mattered. Keep the EA version, symbol, timeframe, broker server, account mode, and test time in the record. This produces evidence that support can use and lets you restore the known configuration.

6. Read the Experts and Journal logs

The log message nearest the attempted action is usually more useful than the visible chart. Open the Toolbox and inspect both Experts and Journal. MetaTrader's official platform logs documentation distinguishes them: the Experts tab contains messages from EAs and indicators, while the Journal records platform events and trade operations. A product message may explain why a setup was skipped; the platform or broker response may explain why a submitted request failed.

Look for the first relevant warning or error, not only the last repeated line. Common categories include disabled automated trading, invalid volume, invalid stops, insufficient funds, a closed market, no connection, an unsupported filling or order mode, and failed initialization. The exact wording matters. Copy the complete timestamped row and the few surrounding rows because a later message can be a consequence of the first failure.

When sharing logs, redact the account number if desired and remove passwords, license secrets, API keys, private keys, payment information, and unrelated personal data. Do not redact the EA name and version, exact symbol, timeframe, broker server, account mode, timestamp with timezone, or error text; those details are often necessary to reproduce the issue. The general YoForex troubleshooting page provides the support path for problems beyond this checklist.

7. Isolate the cause with Strategy Tester and demo checks

Run one controlled Strategy Tester pass using the same EA version, preset, intended symbol, and timeframe. MetaTrader's official Strategy Tester documentation explains how the tester runs an EA on historical data and exposes its results and journal. Use an appropriate test period with enough data and inspect the test journal. A successful historical test shows that the EA can initialize and act under those simulated conditions; it does not prove future profitability or identical live execution.

Interpret the comparison carefully. If the tester produces no trades, inspect initialization, inputs, symbol selection, history, and entry conditions. If the tester trades but a demo account does not, focus on live terminal permission, current market conditions, symbol specification, and broker responses. If demo works but a live account does not, compare the exact server, account authorization, account mode, symbol, volume limits, margin, and broker restrictions. If the behavior is intermittent, preserve timestamps and look for session, spread, connection, or filter patterns.

Do not use a backtest as a reason to bypass a live rejection. Tester data, tick modeling, execution delay, and symbol settings may differ from the connected account. For a broader assessment of tests, drawdown, costs, and evidence, use the guide to evaluating a forex EA before relying on any automated strategy.

8. Prepare a product-specific support handoff

If the cause is still unclear, send support one compact, reproducible case. Include the product name, exact EA version, preset name, MT5 terminal build, operating system, broker and server, demo or live status, hedging or netting mode, exact symbol and timeframe, observed time with timezone, and the relevant Experts and Journal lines. Describe what you expected and what happened. For example, “the EA initialized, but the Journal recorded this rejection at 14:32 UTC” is more actionable than “it does not work.”

Include screenshots of the EA's chart status, its non-sensitive inputs, the symbol specification, and the log area if they help. Never include a trading password, email password, API credential, private key, recovery code, or full payment details. Use the YoForex contact page for a YoForex product and keep the EA running on a demo account only if support asks for additional observation. Support can diagnose documented software behavior; it cannot guarantee that market conditions will create an entry or that a future trade will be profitable.

Common questions about an MT5 EA that will not trade

Why is Algo Trading enabled but the EA still does nothing?

The toolbar switch is only one permission. The individual EA may still have trading disabled, an account or profile change may have triggered a protective setting, the login may be read-only, the EA may have failed initialization, or its entry conditions may not be satisfied. Check the chart status and both logs before changing inputs.

Does no error in the Journal mean the EA is working?

Not necessarily. The EA may write its decision to the Experts tab, may log only initialization events, or may be waiting without producing a message. Confirm that it is attached and enabled, then compare current conditions with its documented filters. A quiet Journal rules out some platform failures but does not prove that an entry exists.

Can an MT5 EA run from the mobile app?

An EA runs in a compatible desktop or hosted MetaTrader environment, not inside the MT5 mobile application. The phone can be used to monitor an account, but closing the desktop terminal or disconnecting the hosted environment can stop EA processing. Follow the environment requirements in the current product documentation.

Should I reinstall the EA or MetaTrader immediately?

Usually not. First save the preset and logs, identify the loaded EA version, verify permissions, and read the first error. Reinstalling can erase the state needed to diagnose a path, permission, or configuration problem. Reinstall only when the evidence points to a missing or damaged file, and use the official product package and documented installation path.

How long should I wait for the first trade?

There is no universal waiting time. It depends on the programmed entry rules, selected symbol and timeframe, market session, filters, and current prices. A provider should explain the EA's workflow but should not promise a trade by a certain time. Use logs and a controlled test to verify operation instead of treating frequent trading as proof that the software is healthy.

Where can I continue learning before using an EA?

Start with the MT5 EA installation and testing guide, then use the YoForex learning and documentation hub to find the exact product manual and independent evaluation checklist. Keep a demo-first record of versions, settings, test conditions, and logs. That record is useful for troubleshooting and for deciding whether the EA's documented behavior fits your account and risk limits.