BUG: Signal-Service closed wrong Position - page 2
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
@Sergey Golubev
I know the problem with deposits/withdrawals - I've hit them several times.
But that was not the case
and I've never made trades by myself in this account
@Eleni Anna Branou
I can't believe that this is only affecting me. May other people do not spent so much time in investigating why they've made losses, and just cancel the abo.
Yes, there may are slippage issues, but that's not the problem.
As in my original post, all operations are correctly done, but sometimes on the wrong position...
look at the attached screenshots.
Check the times on the blue arrows. I'm really really sure, that the wrong position was closed. Not only based on provider's profit and my loss, also based on the open times.
This whole thing is done automatically and cannot be altered on an individual basis, so if it doesn't work well for you there is nothing to be done.
Of course the whole thing is done automatically and of course it can't (and shouldn't) be altered on an individual basis.
But, if there is a bug in it, you should also be interested in getting it fixed...
i've found another thread with the same problem: https://www.mql5.com/en/forum/359951
suggestion:
if the signal-service would set the originating Order-ID as a comment for the copied position (instead or in addition to the (useless) signal-name) and the signal-website (eg https://www.mql5.com/en/signals/540423) would show this Order-ID as well, there will never be any confusing questions about wrong trades etc.
This would help a lot for troubleshooting and finding any errors. So the subscriber can exactly comprehend what's going on (very very useful, especially if positions are opened/closed with delays (eg. slippage))
...
But, if there is a bug in it, you should also be interested in getting it fixed...
...read post #26 about the general idea how to prove it.
Prove is a very strong word.
- If you'd follow my suggestion in the previous post, i'd have some unique identifiers and would be able to prove something
- If you'd send me the source code of MT4, i'd be able to check it and maybe i could find the wrong code and it's proved
But with my limited access to the resources and informations, the only "prove" i can make, is a stupid screenshot of the position, which was incorrectly closed. This is attached in https://www.mql5.com/en/forum/348704#comment_21498737 and another in the original Post.
The Terminal-Version is also mentioned (https://www.mql5.com/en/forum/348704#comment_21489141)
For the original case, i sent the log (as response to https://www.mql5.com/en/forum/348704#comment_17770236) to Marsel via PM
For this case, the log was unfortunately deleted, but i've had a look on it when it happened and it looked exactly the same. (there is also a screenshot of the log in the original post)
So could you please be more specific in what you want me to do, or which informations i should provide?
I'm pretty sure that there is a bug and it'll happen again. So if I know which informations you expect and which screenshots i should take etc., i'll be able to provide them - at least the next time, this happens
Thank you
Hi,
I've had a close look at the log for the case in the original post from 2020-08-05
In fact, I didn't check the start of the Log, only the lines, where the wrong position was closed. But the Initial Synchronization of the Positions (after (re-)starting the Terminal) is wrong (and the same id's were used, when the wrong position was closed)
I've made another Image with many lines to prove the bug.
The final result is: The copied position is older than the original (according to the log)
I've attached the new image (it contains the same screenshots as the original posting)
and the log (as sent to Marcel via PM)
Happy Easter!