Blocks with intermittent problems.

[OntradingX]

@fxDreema I have some projects in progress that are being greatly impaired when they are running on real accounts at different brokerages. I can't share it here but if you call me in the chat I can share the project with you.
These blocks that are in the image are currently showing the reported problems.

This " Position created " block should only execute 1x everything below it whenever any order is opened.
His flashing is:

1. Sometimes it is not executed when the order is opened.
2. When it is executed, it doesn't execute that one time, it happens 2 or more times, it happened 17 times, so as a rule of thumb I put it for him every time he opens a BUY HE hangs a sell on the opposite side, but it's only 1, he then opens a BUY and hangs sometimes 17 sales or 3 sales, it's random, every hour something happens with this block.
   

The " loop pass n times " block should, according to the description of the block, do (execute the number of times that the next block is filled in), I have pending sales orders in the next block, so I consider that if it is defined in this block the number 50, he should then place 50 sell orders at the price I set.
In some moments it does it correctly and in other moments it doesn't, it doesn't matter the number of orders, it can be 50, 1 or 10 orders, it does what it wants, I'm using a formula to calculate the number of orders following times that should be placed pending, this variable is linked to this block, but this block is not consistently respecting it, at some point it fails and places more orders at a time, and at another time less orders, and there are times when it places the requested quantity.

The " Trailling Stop" block was working perfectly, I always put it in "ontick" but I noticed that it is also having an intermittent behavior, it is triggering with a delay, or else at points where it was not requested to trigger.
Today I took a case that I set.
Trailling start to trigger at 1700 points
Moving stop loss to 200 points i.e. would have 1500 points of profit.
Walk every 100 points.
Unfortunately he was triggered with 4260 points.
I didn't understand the reason for this behavior, because the brokerage was normal, with ticks happening, no problem I detected on the brokerage side.

[l'andorrà]

Without seeing the project no accurate suggestions can be made. There can be several reasons for that to happen, and the most likely is that MQ5 is being changed...again.

[OntradingX]

@l-andorrà
I really believe that the problem is in mq5 of fxdreema, because I asked a colleague to do exactly the same as I did in fxdreema but in pure mql and he did it, the result was that in pure MQL, it worked. In Fxdreema, however, it doesn't work, so I believe that the admin should thoroughly check each of these blocks, after what happened with the hacker attack, I realize that a lot of things were out of order, it's very sad to have no answers or solutions.
I'm about to give up using the tool.

[roar]

I use the loop block every day, no problem whatsoever. Please make some kind of example project

[OntradingX]

I cannot share this project with you, I already mentioned above. I already shared the entire project with the admin who owns fxdreema.
I'm waiting for his answers.

[roar]

@OntradingX you cant think of any example of a loop that will not reveal your whole project?
Admin will also ask for a smaller example.

[fxDreema]

I have to say this once again. If anyone suspects a bug, please, make a simple project with the minimum blocks required (should be no more than 4-5 blocks) to demonstrates the bug + short explanation of what is expected to happen.

Sorry, but I don't have this will to dissect projects with 100s of blocks, and even worse - containing many input properties, which will probably be way different on my end.

I ran your project in my tester for a period of 1 year and guess what - I got only 2 positions for the whole time. I don't know why, but I don't want to know why. I just want a simple example, that when I run it, it will fail.

Don't forget that if you (I mean everyone) understand your project, this doesn't mean that I understand it.

When there is a bug, I really want to fix it, but I don't want to explore anyone's projects, strategies and ideas, while searching for a bug that may not even appear on my side at all.

How to make such example?

• Download the project as .mq5 file, then import it back. A new project will be created. Maybe rename the new one. Still ensure that the original project is still there.
• Start deleting blocks. First delete those blocks who surely have nothing to do with the problem. At this point maybe half of the blocks should be gone.
• Continue deleting other blocks. While deleting blocks, test to see that the problem still remains. If the problem goes away, return one or more steps back (un-delete blocks).
• Repeat this until very few blocks remain, and the problem still remains. Leave only the Buy or the Sell side.
• If indicators are not necessary, delete them.
• Remove all input parameters (Constants), because they often lead to unnecessary confusions.
• Remove the Variables as well, unless they are needed for the problem to appear.
• The final example should look nothing like the original project. It should contain less than 10 blocks for sure.