Why is my expert advisor not placing any trades?

The most likely cause is a disabled Algo Trading button in MetaTrader 5. Check that the button at the top of the terminal window is green, not gray. Other common causes include mismatched chart timeframe, insufficient chart bars for indicator calculations, or blocked DLL imports.

What prop firms allow expert advisors on funded accounts?

FTMO allows expert advisors on real funded accounts but restricts martingale and grid strategies during the evaluation phase. MFF permits EAs after passing the challenge. Always verify the current policy of each firm before deploying an EA, as rules change.

Can an expert advisor work on renko charts?

A standard EA designed for time-based candlestick charts will not trigger correctly on renko bars. Renko expert advisors need specialized code that processes brick formations instead of time intervals. You can build a renko-compatible EA by describing the brick logic in natural language with Pineify.

Can I run an expert advisor on stock market symbols?

Yes, MetaTrader 5 supports stock symbols through CFD contracts, and expert advisors can trade them with the same MQL5 logic used for forex pairs. Verify the broker symbol naming convention (AAPL versus AAPL.NYSE) and check that stock market hours match the EA time filter.

How do I evaluate expert advisor performance metrics?

The three key metrics are win rate, maximum drawdown, and profit factor. A win rate below 50% is acceptable if the profit factor exceeds 1.5. A maximum drawdown above 20% with 1% fixed-fractional risk suggests the strategy is overfitted or the risk parameters are misconfigured.

Why did my expert advisor stop working after a MetaTrader update?

MetaTrader updates occasionally change function signatures or deprecate MQL5 functions that your EA relies on. The EA may fail to compile or load after the update. Recompile the EA in MetaEditor or regenerate it with Pineify to ensure compatibility with the current MetaTrader build.

How do I know if my expert advisor has a coding error?

Open the Journal tab in MetaTrader. Initialization errors, compilation errors, or runtime exception messages appear there. The Experts tab also logs EA-specific output. If the EA loads without errors but behaves unexpectedly, the error is in the strategy logic, not the code syntax.

Expert Advisor Not Working? Common Causes and How to Fix Them

An expert advisor not working typically traces to one of three root causes: a MetaTrader configuration issue, a broker or account restriction, or a flaw in the EA logic itself. Identifying which category the problem falls under cuts debugging time from hours to minutes.

Key Takeaways

The Algo Trading button being disabled is the single most common reason an expert advisor is not trading, and it is also the fastest fix.
Broker and prop firm restrictions vary widely; always verify EA policy before deploying on a funded or evaluation account.
An EA that backtests well but fails live likely has curve-fitted parameters; walk-forward and Monte Carlo validation reveal true stability.
Chart symbol, timeframe, and bar count must match what the EA expects; renko and stock market EAs need special configuration.
Pineify generates readable MQL5 code and includes Strategy Optimizer validation, helping you identify and fix EA issues before live deployment.

Why Your Expert Advisor Is Not Trading on MetaTrader

The most common reason an expert advisor is not trading has nothing to do with the strategy. The Algo Trading button in MetaTrader 5 must be green. If it is gray, no EA fires any order regardless of its code. I generated an EURUSD breakout EA in MQL5 using Pineify and dropped it on the H1 chart. Two hours passed without a single trade. The backtest showed consistent signals, yet live ticks produced no action. The Journal tab showed the EA loaded without errors. The fix: auto-trading was disabled in Tools > Options > Expert Advisors. One checkbox fixed everything. Other common configuration failures include: running an EA coded for EURUSD on GBPUSD, attaching to a chart without enough bars for indicator calculations, and blocking DLL imports when the EA requires them.

Algo Trading button must be green; gray button blocks all EA orders
EA coded for one symbol (EURUSD) will not fire on a different chart
Insufficient chart bars prevent indicators like 200-period SMA from computing
DLL import blocking stops EAs that need external libraries for computation
Journal tab shows EA load status and specific initialization errors

Broker and Prop Firm Restrictions on Automated Trading

Not all brokers allow expert advisors on every account type. Cent accounts, Islamic swap-free accounts, and demo accounts with limited tick data often disable automated trading. Prop firms such as FTMO, MFF, and others restrict EA usage during evaluation phases to prevent martingale or grid strategies from gaming the profit target. Some prop firms permit EAs only after passing the challenge or restrict EA usage to specific symbols. What prop firms allow expert advisors depends on the firm: FTMO allows EAs on real funded accounts but restricts certain high-frequency or martingale strategies, while others ban all automated trading during challenges. US brokers enforce FIFO rules that close positions in the order they were opened, which breaks hedging expert advisors that try to maintain multiple positions on the same symbol.

Cent accounts and Islamic accounts may have automated trading disabled by default
FTMO and MFF restrict certain EA types (martingale, grid) during evaluation
US broker FIFO rules break hedging EAs that open multiple positions on one symbol
Demo accounts with limited tick history can prevent EA initialization
Always check your broker EA policy before deploying on a live account

Expert Advisor Logic Failures and Performance Metrics

Sometimes the EA loads and runs without errors but still loses money or never triggers. This is a logic failure, not a configuration problem. An EA that backtested at a 68% win rate on EURUSD data from 2020 to 2023 may have curve-fitted its entry conditions to that specific market cycle. When market conditions shift into a low-volatility range environment, the same breakout EA may fire two false signals per month instead of ten profitable ones. Expert advisor performance metrics like drawdown percentage, win rate, and profit factor reveal whether an EA has genuine edge or statistical noise. A win rate above 60% with a profit factor below 1.5 often signals curve fitting rather than reliable logic. Fixed-fractional position sizing at 1% risk per trade and a maximum drawdown below 20% are standard benchmarks for evaluating any EA.

An EA that works in backtest but fails live likely suffers from curve fitting
Win rate above 60% with profit factor below 1.5 signals statistical noise
Maximum drawdown below 20% with fixed-fractional 1% risk is a standard benchmark
Walk-forward analysis reveals whether EA logic holds across different market regimes
Pineify Strategy Optimizer tests EA parameter stability with Monte Carlo simulation

Chart, Symbol, and Timeframe Compatibility for EAs

An expert advisor coded for renko bars will not trigger on a standard candlestick chart. Renko expert advisors plot trades based on brick size, not time, and require the MetaTrader renko chart indicator or a custom script to generate bricks. Many EAs default to the chart symbol and timeframe they were dropped on. If your EA was designed for XAUUSD on H4 and you attach it to US30 on M15, the entry conditions may compute without ever finding a valid signal. Stock market expert advisors require correct broker symbol naming (AAPL on some brokers is AAPL.NYSE). Multi-currency EAs need all referenced symbols visible in Market Watch. If any symbol is hidden or the market is closed, the EA may report initialization errors without explaining which symbol caused the failure.

Renko EAs need renko brick generation; standard candle charts will not trigger them
EA designed for XAUUSD H4 will rarely produce valid signals on US30 M15
Stock market symbol naming varies by broker: AAPL may be AAPL or AAPL.NYSE
Multi-currency EAs require every referenced symbol in the Market Watch list
Closed markets on weekends prevent EA initialization on those symbols

Step-by-Step Diagnosis for a Non-Working Expert Advisor

Start with the Journal tab. It logs every EA load, unload, and runtime error. If the EA loaded without errors but placed no trades, check the Algo Trading button and verify the chart timeframe matches the EA code. Open the strategy tester and run the EA on the same symbol and period you are using live. If the tester produces trades but the live chart does not, the issue is a runtime configuration, not the EA code. If the tester also produces no trades, the EA logic contains a condition that is never met in current market data. You can inspect the input parameters and adjust thresholds such as a 20-period ATR filter that is too wide for the current volatility regime. Pineify generates readable MQL5 code, so you can open the EA file and see every condition without decoding obfuscated script.

Check Journal tab for EA initialization errors and runtime exceptions
Verify Algo Trading button is green and chart timeframe matches EA code
Run the same EA in strategy tester to isolate configuration issues from logic issues
Adjust parameters like ATR filter width or RSI threshold if tester produces no trades
Pineify generates readable MQL5 code so you can inspect logic without manual coding

Related Resources

Generate an MQL5 expert advisor with Pineify Free MT5 Expert Advisor Download Strategy Optimizer for EA Backtesting What Is an Expert Advisor? Complete Guide

This page is for informational purposes only and does not constitute investment advice. Trading with automated expert advisors carries substantial risk of loss. Past performance does not guarantee future results. Always consult a qualified financial advisor before making trading decisions.