Interesting topic for many: what's new in MetaTrader 4 and MQL4 - big changes on the way - page 54
![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Sometimes it can happen that on the UPU computer the order is activated and shows in the list of orders, but not on the home computer. And vice versa. The situation is even worse when it is shown on the home computer and not on the UPU. This means that the EA does not notice that the order is activated, with all ensuing consequences. We have not yet found out the signs of when it appears. However, it usually happens when I trade intensively enough or at the very beginning, at the first trade after the terminal has been opened. If you close-open the terminal or re-login the order appears in the list and usually no more failures are observed.
It's about the mismatch between the order tables of the terminal and the trading server. The real important thing will be done - if you fix it.
Please give me the ticket numbers of Service Desk, please.
Now that we're talking about it: in MT4, pending orders in the tester are triggered at their own prices even if there were no such prices, i.e. if you place a pending order and there is a gap, the order will trigger within this price gap, which in reality cannot happen and is just another way to build a tester grail. We should fix the "chip".
Please provide servicedesk ticket numbers.
#473685 - closed last year still without explanation. The problem was relevant today (traded a bit) on an extreme MT4 build.
If we are going to do that, in MT4 there is such a "trick", in the tester, pending orders are triggered at their own prices even if there were no such prices, i.e. if we place a pending order and there is a gap in price, the order will trigger within this price gap, which in reality cannot happen and that is one more way to build a tester grail. We should fix this "thing".
The problem of negative slippage not being taken into account only applies to stop positions (including SL levels). Limit orders are more or less OK.
The only thing is that in Potik testers there is always an option - to execute a limit order (you can do it for stop orders as well) at the price of the order or at the first satisfying price. Of course, there is no such an option in MT4, because testing on custom tick history is an optional feature of MT4.
The ticket has been raised again, we'll look into it.
If we are going to do this: there is such a thing in MT4, in the tester pending orders trigger at their own prices even if there were no such prices, i.e. if we place a pending order and there is a gap, it will trigger inside this price gap - in reality it cannot happen and it is one more way to build a tester grail. We should fix the "thing".
Why is only MetaTrader 4 mentioned?
Both Take Profit and Stop Loss work within gaps.
After all, MetaTrader 5 and MetaTrader 4 work the same way in these cases, here are concrete examples with code https://www.mql5.com/ru/forum/1031/page18#comment_530271
Why is only MetaTrader 4 mentioned?
Both Take Profit and Stop Loss work within gaps.
After all, MetaTrader 5 and MetaTrader 4 work the same way in these cases, here are concrete examples with code https://www.mql5.com/ru/forum/1031/page18#comment_530271