Issue with Virtual Hosting a Close Command on its own
Your EA is broken; fix it.
EAs must be coded to recover. If the power fails, OS crashes, terminal or chart is accidentally closed, on the next tick, any static/global ticket variables will have been lost. You will have an open order but don't know it, so the EA will never try to close it, trail SL, etc. How are you going to recover? Use a OrderSelect / Position select loop to recover, or persistent storage (GV+flush or files) of ticket numbers required.
On a network disconnection you might get ERR_NO_RESULT or ERR_TRADE_TIMEOUT. There is nothing to be done, but log the error, return and wait for a reconnection and a new tick. Then reevaluate. Was an order opened or is the condition still valid.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi,
My VPS issued a close command on its own, causing my EA not to function as expected (please see attached screenshot).
The thing is, Today I noticed that some of the positions that are supposed to be closed by my EA did not close at all. Looking at the logs, the EA stopped working due to the close command issued by the VPS.