MT5 trade context is busy

Causes, most likely first

1. Two EAs tried to trade at the same moment

MetaTrader processes one trade operation at a time per terminal. Two Expert Advisors on different charts that both fire on the same tick will collide, and one gets refused. Running several EAs in one terminal is the usual root cause — see running multiple bots.

2. A manual order was placed while the EA was working

Clicking a trade in the terminal while an EA is mid-operation produces exactly this. Harmless once, and a real problem if you trade manually alongside an automated system on the same account.

3. The previous operation has not completed

A slow fill, a requote or a broker-side delay holds the context open. An EA that fires again before the first request has returned collides with itself, which looks like a broker problem and is not.

4. The EA does not wait or retry

The correct handling is to wait briefly and retry once, not to abandon the signal and not to loop. An EA that treats a busy context as a hard failure silently drops trades it should have taken, and nothing in the account history records the ones that never happened.

Why this happens

This error is about the terminal, not the market or the account. Nothing is wrong with your balance, your symbol or your strategy — two things simply asked to trade at the same instant.

The reason it matters more than it looks is that the missed trade leaves no trace. A rejected order appears in the Journal; a signal the EA decided to skip does not appear anywhere. If results diverge from a backtest and the Journal shows busy-context messages, that gap is a candidate explanation.

The clean fix is one terminal per EA. Isolation costs a little more resource and removes an entire class of collision.