Pineify logo

MQL4 ERR_TRADE_DISABLED

MQL4 error 133 trade disabled: what to check

MQL4 error 133 trade disabled maps to ERR_TRADE_DISABLED: trade is disabled. The restriction can come from the symbol, account, broker, or server session rather than the order syntax. For API calls, check the return value and capture GetLastError after a documented failure. Critical runtime errors require preventive guards and inspection of the terminal log.

See where Pineify fitsReview the code example
TradePermissionDiagnostic.mq4MQL4
#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 disabled
  • Check API results or the runtime failure log
  • Capture relevant inputs and error context
  • Retry only when the condition can change

What MQL4 error 133 means

The official MQL4 runtime table names error 133 ERR_TRADE_DISABLED and defines it as “trade is disabled.” The restriction can come from the symbol, account, broker, or server session rather than the order syntax.

An error-state value is supporting context, not proof that a call failed or a diagnosis of the whole EA. For noncritical API failures, read the return value and then GetLastError, which resets _LastError. Critical errors such as zero division terminate execution, so code after the failing expression cannot serve as a recovery handler.

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.

  • The broker has disabled trading for the symbol or account
  • The symbol is view-only, expired, or outside its supported session
  • The account connection or investor-password session cannot trade
  • The EA treats a server restriction as a code-format error

Fix the cause, then choose a retry policy

Do not loop on the same request. Retry only after the symbol, account, session, or broker restriction has changed.

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
The broker has disabled trading for the symbol or accountCheck the symbol trading state and ask the broker when server-side trading is disabled.
The symbol is view-only, expired, or outside its supported sessionUse a currently tradable symbol and session without silently substituting another market.
The account connection or investor-password session cannot tradeReconnect with a trade-enabled account and verify terminal permissions.
The EA treats a server restriction as a code-format errorLog the restriction and stop submitting orders until the external state changes.

Review the complete example

The skeleton checks connection and local trade availability; its entry logic is only a comment. It does not query symbol trading status or place an order. IsTradeAllowed alone cannot distinguish every server restriction, and repeated tick logs need throttling.

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

TradePermissionDiagnostic.mq4MQL4
#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

    Locate the failed operation

    Check the API result, or the terminal log and source location for a critical runtime failure.

  2. 2

    Capture the error once

    For a recoverable API failure, capture GetLastError immediately. For a terminated program, preserve the terminal log. Record error 133 and the inputs relevant to the failed operation.

  3. 3

    Correct the triggering condition

    Check the symbol trading state and ask the broker when server-side trading is disabled.

  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 133 trade disabled mean?

ERR_TRADE_DISABLED means trade is disabled. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

What usually causes MQL4 error 133?

The broker has disabled trading for the symbol or account. The symbol is view-only, expired, or outside its supported session. The account connection or investor-password session cannot trade. The EA treats a server restriction as a code-format error.

Should an EA retry after error 133?

Do not loop on the same request. Retry only after the symbol, account, session, or broker restriction has changed.

Why should GetLastError be called immediately?

For a noncritical API failure it reports the current _LastError value and resets it. A delayed read may describe another call. It cannot recover execution after a critical error has terminated the program.

Can Pineify fix MQL4 error 133?

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.

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