MQL4 ERR_TRADE_CONTEXT_BUSY

MQL4 error 146 trade context busy: use bounded retries

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. 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.

Open MQL4 Coding Agent Review the code example

Open the Coding Agent, then choose MQL4 from the language menu.

TradeContextDiagnostic.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 context is busy
Check API results or the runtime failure log
Capture relevant inputs and error context
Retry only when the condition can change

What MQL4 error 146 means

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.

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.

Another EA, script, or chart is sending or modifying an order
Multiple EA or script instances check availability before one occupies the shared trade context
Retry code has no delay, attempt limit, or shared lock
A slow server response keeps the terminal trade context occupied

Fix the cause, then choose a retry policy

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	Coordinate order submission among the EA and script instances sharing the terminal.
Multiple EA or script instances check availability before one occupies the shared trade context	Treat availability checks as observations, not a lock; handle a later trade-call rejection too.
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.

Review the complete example

The skeleton checks connection and IsTradeAllowed; it contains no trade request, lock, or retry scheduler. Add coordination and bounded rescheduling for participating EA instances, and throttle repeated tick logs.

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

TradeContextDiagnostic.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
Locate the failed operation
Check the API result, or the terminal log and source location for a critical runtime failure.
2
Capture the error once
For a recoverable API failure, capture GetLastError immediately. For a terminated program, preserve the terminal log. Record error 146 and the inputs relevant to the failed operation.
3
Correct the triggering condition
Coordinate order submission among the EA and script instances sharing the terminal.
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 146 trade context busy mean?

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

What usually causes MQL4 error 146?

Another EA, script, or chart is sending or modifying an order. Multiple EA or script instances check availability before one occupies the shared trade context. Retry code has no delay, attempt limit, or shared lock. A slow server response keeps the terminal trade context occupied.

Should an EA retry after error 146?

Use bounded backoff and recheck IsTradeAllowed before each attempt. Never spin in an infinite loop or block the terminal while waiting.

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 146?

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.

Official references

Related MQL4 resources

MQL4 error code reference Error handling in MQL4 MQL4 AI Coding Agent

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