MQL4 ERR_TRADE_DISABLED
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. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.
#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.
}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.
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.
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.
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.
| Check | Action |
|---|---|
| The broker has disabled trading for the symbol or account | Check the symbol trading state and ask the broker when server-side trading is disabled. |
| The symbol is view-only, expired, or outside its supported session | Use a currently tradable symbol and session without silently substituting another market. |
| The account connection or investor-password session cannot trade | Reconnect with a trade-enabled account and verify terminal permissions. |
| The EA treats a server restriction as a code-format error | Log the restriction and stop submitting orders until the external state changes. |
The EA checks connection and local trade availability before evaluating an entry. These checks improve diagnosis but do not prove the broker will accept the order.
The example improves validation and logging. It does not prove the operation will be accepted by a broker or behave safely in live trading.
#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.
}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 AgentStatic diagnostics do not prove runtime behavior, backtest results, broker compatibility, or live-trading safety.
Check the API return value before interpreting an error number from the log.
Call GetLastError immediately and record error 133, symbol, prices, volume, ticket, and terminal state relevant to the operation.
Check the symbol trading state and ask the broker when server-side trading is disabled.
Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.
ERR_TRADE_DISABLED means trade is disabled. The code should still identify which API returned failure and log the inputs used for that call.
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
Do not loop on the same request. Retry only after the symbol, account, session, or broker restriction has changed.
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.
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.
Define the requirement, inspect the generated source, repair diagnostics, and test the behavior in your own MT4 environment.
Open Coding Agent