AutoTrading is one check, but switching it on alone does not mean the EA will generate an order or that an order will execute. Enable it only after you trust the EA and intend to use it on that account, then work through the checks below.
Expert Advisors (EAs) cannot be installed or run in FXTRADING.com App.
Common Reasons for EA Trade Execution Issues
When trading with FXTRADING.com, there are several potential reasons why your Expert Advisor might not be executing trades as expected:
Basic Setup Issues
Automatic trading permission: In MT4 desktop, check both the terminal-wide permission and the permission for the EA attached to the chart. If either blocks trading, the EA may still analyse prices without being allowed to send trades. A toolbar colour alone does not identify the cause.
EA Not Attached to Chart: Verify the EA is properly attached to the relevant chart
Wrong Symbol or Timeframe: Confirm your EA is attached to the correct currency pair and timeframe it was designed for
Technical Limitations
Available margin: Compare the proposed trade's margin requirement with the account's available margin. Balance alone does not show how much margin remains after existing positions and other requirements.
Trading Restrictions: Check if your account has any trading restrictions
Market Closed: The market for the instrument you're trying to trade may be closed
Internet Connection Issues: Unstable internet connection can prevent EA execution
EA Configuration Problems
Incorrect Settings: Review your EA's input parameters
Compatibility Issues: Ensure your EA is compatible with the MT4 version you're using
Programming Errors: The EA code itself may contain errors or logical flaws
Missing DLLs or Libraries: Some EAs require additional files to function properly
Trading Conditions
Slippage Settings: Your EA may have restrictive slippage settings
Spread Limitations: Some EAs won't trade if the spread exceeds a certain threshold
Lot Size Restrictions: The EA might be attempting to trade with a lot size not permitted on your account type
How do I fix EA execution issues?
Check trading permission deliberately: First confirm the intended account, server, attached EA and its inputs. Allow automated trading only if you trust the program and intend it to trade on that account; review both permission levels rather than repeatedly toggling the toolbar button.
Preserve the relevant records before restarting: Note when the issue occurred and save the nearby log messages before closing MT4. If you restart, confirm the account, attached EA and trading permissions again before resuming use.
Read both log types: Check the platform's Journal and the EA's Experts messages for the same incident. Follow the explanation below to distinguish a program message, a trade request and its result.
Review EA Settings: Double-check all input parameters
Test in Strategy Tester: Use the strategy tester to identify potential issues
Contact the EA Developer: If you purchased the EA, reach out to its developer
Check Permissions: Enable only the permissions the EA actually requires after reviewing its source or provider. Do not enable DLL imports or external access unless you understand and accept the specific need.
Separate the stages: The EA may be running but waiting for its programmed entry conditions, may be unable to send a trade request, or may have sent a request that was rejected. Compare the EA's records with the terminal's expert and system logs and the exact error before choosing a remedy. Do not loosen spread, volume or risk limits merely to force a trade.
After changing an account, profile, chart symbol or timeframe, a protective MT4 setting may disable automated trading. Recheck the active account, EA and permission state. Do not disable that protection automatically or treat the absence of a new trade as proof that the EA is faulty.
How to read and preserve EA logs
In MT4 desktop, show the Terminal window from the View menu, or use Ctrl+T on Windows. The Journal records platform events, including startup, connection and trading operations. The Experts tab contains messages from the attached EA. Some empty tabs may be hidden; an absent Experts tab does not establish why no trade occurred.
Read messages immediately before and after the incident, matching the time and symbol. A program-loaded message does not prove that a trade request was sent or executed. If the records show no request, check the EA's entry conditions with its developer. If a request was rejected, preserve the exact error and check the relevant account and instrument conditions rather than changing settings at random.
For an older incident, right-click a log entry and choose Open to access its dated log files. MT4 platform logs are in Logs and EA logs in MQL4/Logs; daily filenames follow YYYYMMDD.LOG. The visible tabs show recent entries, so a missing older line is not proof that the event never happened. Keep the relevant time range before clearing a tab or restarting.
In MT5 desktop, the corresponding Journal and Experts tabs are in the Toolbox window. Platform files are in Logs and EA files in MQL5/Logs. MT5 journal times follow the computer's timezone; record that timezone and check it against the trade-history time before comparing events. Do not assume the two clocks are identical.
Choose the correct record for the problem: MetaEditor's compilation errors concern building the program, while the Strategy Tester's journal concerns a test run. Neither proves a live trade was executed. Share only the relevant, redacted incident records through the support route below, not the entire platform data folder. Do not place another trade merely to produce a log.
Use records to identify the cause
Before changing settings repeatedly, note the platform and version, account type and server, symbol, date and time with timezone, whether the EA was attached and enabled, and the exact Journal or Experts message or order error. A redacted screenshot can help. Do not include passwords, one-time codes, private keys, recovery phrases, identity documents or full payment details.
The Customer Support Team can review current FXTRADING.com account, platform, server, symbol, trading-condition and FXTRADING.com error records. It cannot audit, debug or approve third-party EA code or strategy; contact the EA developer for that. A setting change, Strategy Tester result or support review does not guarantee that an EA will generate an order, that an order will execute, or any trading result.
Related information: Trading bot policy; Using EAs on trading platforms; Submit evidence through Service Hub