MQL4 ERR_TRADE_CONTEXT_BUSY
MQL4 error 146 trade context busy maps to ERR_TRADE_CONTEXT_BUSY: trade context is busy. Another trade operation is still using the terminal trade context, so the current request cannot run yet. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.
Open the Coding Agent, then choose MQL4 from the language menu.
#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 146 ERR_TRADE_CONTEXT_BUSY and defines it as “trade context is busy.” Another trade operation is still using the terminal trade context, so the current request cannot run yet.
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.
Use bounded backoff and recheck IsTradeAllowed before each attempt. Never spin in an infinite loop or block the terminal while waiting.
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 |
|---|---|
| Another EA, script, or chart is sending or modifying an order | Serialize trade operations within the EA and across its event paths. |
| The same EA starts a second trade operation before the first finishes | Return from the handler while a prior request is active. |
| Retry code has no delay, attempt limit, or shared lock | Use a short delayed retry with a strict attempt limit. |
| A slow server response keeps the terminal trade context occupied | Log elapsed time and stop after the retry budget rather than blocking forever. |
The EA exits the tick when trading is unavailable or the context is busy. A full implementation should serialize its own requests and schedule a later attempt instead of sleeping inside a long loop.
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 146, symbol, prices, volume, ticket, and terminal state relevant to the operation.
Serialize trade operations within the EA and across its event paths.
Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.
ERR_TRADE_CONTEXT_BUSY means trade context is busy. The code should still identify which API returned failure and log the inputs used for that call.
Another EA, script, or chart is sending or modifying an order The same EA starts a second trade operation before the first finishes Retry code has no delay, attempt limit, or shared lock A slow server response keeps the terminal trade context occupied
Use bounded backoff and recheck IsTradeAllowed before each attempt. Never spin in an infinite loop or block the terminal while waiting.
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