Err_trade_timeout (error 128) is trade context busy?

Quick question: Is the tradecontext busy while the system is waiting for a dud trade attempt to timeout?

I am writing code to handle this error but it's a bit difficult to replicate the error. And hard to find info on the internet.

Thanks

for loop = 1 to 10 more or less
if(TradeContextbusy())
Sleep(500)
else
break
//

Thanks for the reply but that didn't answer my question

"Quick question: Is the tradecontext busy while the system is waiting for a dud trade attempt to timeout?"

I don't know what a "dud trade" is. Context is busy when your process can not get a thread to the order server - it could be any number of reasons - other EA on another chart working, manual order entry, whatever. I doubt you can recreate it in an orderly fashion, since it happens when things are very busy. One way perhaps would be to set an EA on a chart that places orders in a loop as fast as it can. Your test (on a separate chart) would likely hit it. But the problem still remains: what to do about it. It is just one of many errors that must be handled.

Hi mate, when a trade timeout occurs the response from the server for your OrderSend/Close/etc request is either non existent or very very late. In my case it was 3 minutes after I initially posted an OrderSend, which is perhaps a preset timeout value inside MT4. It is similar to HTTP request/responses if you want to understand the concept further.

I was already handling tradecontext busy - that is not a problem at all - but my code defaulted to re-trying the OrderSend upon the timeout failure so I ended up with two orders! I've coded logic to handle this situation now based on the suggestion in the help file, but my question remains:

While MT4/EA is waiting for the timeout to occur, is the trade context busy the whole time?

There is little information about this err_trade_timeout but my own experience is that it's a very rare error so I'm not too surprised.