AutoTrading is one check, but switching it on alone does not mean the program will generate an order or that an order will execute. Enable it only after you trust the program and intend to use it on that account, then work through the checks below.

Expert Advisors cannot be installed or run in FXTRADING.com App.

Common Reasons for Program Trade Execution Issues

When trading with FXTRADING.com, there are several potential reasons why your automated trading program 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 program attached to the chart. If either blocks trading, the program may still analyse prices without being allowed to send trades. A toolbar colour alone does not identify the cause.
Program Not Attached to Chart: Verify the program is properly attached to the relevant chart
Wrong Symbol or Timeframe: Confirm your program 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 program execution

Program Configuration Problems

Incorrect Settings: Review your program's input parameters
Compatibility Issues: Ensure your program is compatible with the MT4 version you're using
Programming Errors: The program code itself may contain errors or logical flaws
Missing DLLs or Libraries: Some programs require additional files to function properly

Trading Conditions

Slippage Settings: Your program may have restrictive slippage settings
Spread Limitations: Some programs won't trade if the spread exceeds a certain threshold
Lot Size Restrictions: The program might be attempting to trade with a lot size not permitted on your account type

How do I fix program execution issues?

Check trading permission deliberately: First confirm the intended account, server, attached program 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 program and trading permissions again before resuming use.
Read both log types: Check the platform's Journal and the program's Experts messages for the same incident. Follow the explanation below to distinguish a program message, a trade request and its result.
Review Program Settings: Double-check all input parameters
Test in Strategy Tester: Use the strategy tester to identify potential issues
Contact the Program Developer: If you purchased the program, reach out to its developer
Check Permissions: Enable only the permissions the program 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 program 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 program'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, program and permission state. Do not disable that protection automatically or treat the absence of a new trade as proof that the program is faulty.

How to read and preserve program 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 program. 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 program'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 program 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 program 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.

MT4/MT5: check state that survives a restart

MT4/MT5 programs can use terminal-global variables, separate from their source-code variables. These persist across platform restarts and remain available for four weeks after their last call by an automated trading program or modification. Restarting MT4/MT5 does not clear this state.

In MT4/MT5, inspect the entries without changing them:

Open the Tools menu.
Select Global Variables.

Alternatively, use the standard F3 shortcut. If behaviour persists after restarting, ask the program’s developer whether it uses these variables and what recovery is appropriate.

MT4: read the global-variable fields

Field	What it shows
Name	The terminal-global variable’s identifier.
Value	The stored value, rather than a source-code variable.
Last call time	When the variable was last called; a manual modification also updates this time.

In MT4, double-clicking a name or value cell starts editing it. For diagnosis, read the entries without changing them; do not treat a double-click as a harmless refresh.

Do not edit or delete global variables merely to force a trade; programs can share them. Preserve the incident records described above and follow instructions for the specific program.

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 program 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 program code or strategy; contact the program developer for that. A setting change, Strategy Tester result or support review does not guarantee that a program will generate an order, that an order will execute, or any trading result.

Why Didn't My Automated Trading Program Execute Trades in MT4?