Pineify logo

MQL4 ERR_TRADE_NOT_ALLOWED

MQL4 error 4109 trade is not allowed: permission checks

MQL4 error 4109 trade is not allowed maps to ERR_TRADE_NOT_ALLOWED: trade is not allowed; enable Allow live trading in the Expert Advisor properties. The local EA or terminal trading permission prevents the request before strategy logic can place a live trade. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.

See where Pineify fitsReview the code example
TradeAllowedDiagnostic.mq4.mq4
#property strict

void OnTick()
  {
   if(!IsConnected())
     {
      Print("No terminal connection.");
      return;
     }

   if(!IsTradeAllowed())
     {
      Print("Trading is disabled or the trade context is busy.");
      return;
     }

   // Evaluate the entry rule only after the terminal checks pass.
  }
  • Official meaning: trade is not allowed; enable Allow live trading in the Expert Advisor properties
  • Read the failed API return value first
  • Capture GetLastError immediately
  • Retry only when the condition can change

What MQL4 error 4109 means

The official MQL4 runtime table names error 4109 ERR_TRADE_NOT_ALLOWED and defines it as “trade is not allowed; enable Allow live trading in the Expert Advisor properties.” The local EA or terminal trading permission prevents the request before strategy logic can place a live trade.

The error number is evidence about one failed call, not a diagnosis of the whole EA. Read the API sentinel first, then call GetLastError immediately because that function returns the current _LastError value and resets it.

Check these conditions before editing the strategy

Start with the inputs and external state that existed at the failure point. A later log entry or a successful call can overwrite the useful context.

  • Allow live trading is disabled in the EA properties
  • The terminal AutoTrading control is disabled
  • Account or terminal permissions prevent automated trading
  • The EA checks only its entry signal and ignores execution permission

Fix the cause, then choose a retry policy

Do not retry until a user or terminal setting changes. Code must not bypass or silently change the permission decision.

Keep the original trading and risk rules intact. A workaround that widens stops, increases volume, changes an account setting, or ignores a failed return value can hide the symptom while changing the system.

CheckAction
Allow live trading is disabled in the EA propertiesReview the EA Common settings and enable live trading only when intended.
The terminal AutoTrading control is disabledCheck the terminal AutoTrading state and the account authorization.
Account or terminal permissions prevent automated tradingLog permission state separately from trade-server rejection codes.
The EA checks only its entry signal and ignores execution permissionGate the order path with IsTradeAllowed and stop cleanly when it is false.

Review the complete example

The EA checks connection and IsTradeAllowed before reaching order logic. The user still controls whether automated trading should be enabled.

The example improves validation and logging. It does not prove the operation will be accepted by a broker or behave safely in live trading.

TradeAllowedDiagnostic.mq4.mq4
#property strict

void OnTick()
  {
   if(!IsConnected())
     {
      Print("No terminal connection.");
      return;
     }

   if(!IsTradeAllowed())
     {
      Print("Trading is disabled or the trade context is busy.");
      return;
     }

   // Evaluate the entry rule only after the terminal checks pass.
  }
Where Pineify fits

Move from the rule to editable MQL4 source

Pineify can generate or revise one self-contained .mq4 file with MQL4-specific reference context. Its independent static checker returns MetaEditor diagnostics so you can repair source issues before testing in your own MT4 environment.

Open MQL4 Coding Agent

Static diagnostics do not prove runtime behavior, backtest results, broker compatibility, or live-trading safety.

Pineify MQL4 Coding Agent with MQL4 selected and an editable MetaTrader 4 code artifact

A practical workflow

  1. 1

    Confirm the failed call

    Check the API return value before interpreting an error number from the log.

  2. 2

    Capture the error once

    Call GetLastError immediately and record error 4109, symbol, prices, volume, ticket, and terminal state relevant to the operation.

  3. 3

    Correct the triggering condition

    Review the EA Common settings and enable live trading only when intended.

  4. 4

    Retest in the target environment

    Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.

Frequently asked questions

What does MQL4 error 4109 trade is not allowed mean?

ERR_TRADE_NOT_ALLOWED means trade is not allowed; enable Allow live trading in the Expert Advisor properties. The code should still identify which API returned failure and log the inputs used for that call.

What usually causes MQL4 error 4109?

Allow live trading is disabled in the EA properties The terminal AutoTrading control is disabled Account or terminal permissions prevent automated trading The EA checks only its entry signal and ignores execution permission

Should an EA retry after error 4109?

Do not retry until a user or terminal setting changes. Code must not bypass or silently change the permission decision.

Why should GetLastError be called immediately?

It reports the current _LastError value and resets it. Other operations can change the error state, so a delayed read may describe the wrong call.

Can Pineify fix MQL4 error 4109?

Pineify can revise a self-contained .mq4 file, add validation and error logging, and return static MetaEditor diagnostics. It cannot prove broker acceptance, account permissions, market availability, or live execution.

Last verified against the linked official references on . Compile and test the final source in the MetaTrader 4 build, broker, symbol, and account environment you plan to use.

Continue with one reviewable MQL4 file

Define the requirement, inspect the generated source, repair diagnostics, and test the behavior in your own MT4 environment.

Open Coding Agent