in fairness I was also in the camp of generally "who gives a F" but it was more from the standpoint of being gracious that we have these jobs.
It wasn't I. The point I am making is you are doing very well in your account using your autosystem, and I am saying that if your system is sound, which seems to be the case, these tiny slippages should not hurt you much, considering how much your account size has grown.
Dude I only made like $3500 since launching the algo in September without major errors. I messed up in November cause I was tinkering with overnight hours and also playing around with micro dax and gold. December is when i decided to drop overnight hours altogether and focus on just US session markets. As far as the algo is concerned, I think it's at the final version that I'm happy with. I dont see anymore 'fixes' needed at this point. Just letting it run and see how it does next few months. This algo went through several iterations. Cost me just under $1300 wokring with mt5 devs from third world countries lol.
Found errors today that threw the EA off. In fact found other issues from recent change. end up with bigger loss that I should have on MYM Need to go back to the bracket order version of the EA until this shit is fixed. Working with dev is giving me anxiety
The stupid thing about MT5 is that you wont encounter issues like this in demo environment. Only in live that i can see errors sometimes. WHich makes this process frustrating and costly to test
I thought the dev eliminated all bracket orders. There shouldn't be any value for TP in that stop order. Also very true what you say about the demo environment. Live testing is the final arbiter.
Stupid question, rIght now I'm running the single EA and apply it to 5 different charts. If I renamed the EA into 5 different ones, and apply to each chart, does it make each EA independent and faster to execute?
lol yes. in the demo environment in MT5 when you buy it always buys the bid and selling always sells the ask. utterly ridiculous. I believe you might get interference unless you designate them differently with - wait for this highly technical term - Magic numbers. check with your programmer, they'll know better than me but I'm fairly certain this is the case.
Without knowing the answer as to whether it would be faster to execute or not, in your position I would stick with the single EA, as the status quo would cause the least headaches for your programmer. You may post this question on the MQL5 Forum, and if they say that it would lead to significant improvement (which I highly doubt), you can then implement the changes.