Position Created block with failure.

[OntradingX]

This is a block with issue.
Project to test --> https://fxdreema.com/shared/jjMQq1Z6c

The rule I created is simple, (whenever a group 2 purchase order) is created, so draw a line, with project test I created it is noted that the line is not always designed, but constantly a purchase of group 2 is created.

So I believe this block is not really working as it should work that is whenever there is a negotiation created to go to the next block and execute.

[OntradingX]

@fxDreema

[l'andorrà]

Position created block will only draw the line when the position is hit by price, not when programmed on the chart.

[OntradingX]

@l-andorrà
This is exactly what is not happening, only when the pending order is triggered or when it is (created) that the line should appear, that is why the block is called position created.
The order is being created/opened and the line is not being drawn.
So you agree that there is a bug?

[l'andorrà]

Yes, in that case the problem is a bug. But is there anything else conflicting that part of the bot? Is that the whole bot or just part of it?

[OntradingX]

@l-andorrà
I take a part of the robot and generate another project and put the same situation to happen and reproduce the same error.
I don't see the need to post an entire robot that has lots and lots of blocks in my language that no one will understand to check if there is a conflict in logic or something.
This problem was already posted a few days ago in the bugs area and I'm waiting for answers from the admin.

[QuantEngineer]

I am also finding a problem in the "Position Created" Block... I have isolated the issue to a minimum project, where it becomes really easy to reproduce the issue....

The only purpose of this project is to detect when a position is created...

[QuantEngineer]

For some reason, this is what happens in the log... Only the first time that the block runs, it works correctly... after that, is has some unexpected behavior where it runs multiple times even if the user only opens 1 position... and it runs also even if the user "closes a position"

[QuantEngineer]

Here is the link to the test project
https://fxdreema.com/shared/B5sSQ70Wc

[QuantEngineer]

If anyone has any experience with this, welcome to share

[OntradingX]

@QuantEngineer Thanks for contributing.
This is exactly what is happening and it is very important for this block to function properly. I think he is one of the most important.
@fxDreema Can you please help us ?

[QuantEngineer]

Today, I just noticed that the block "Position Created" is also triggering as a false positive when a position is closed...
I was even working on a custom block to detect false positives, but when it happens, the ticket comes with a different number... a

[QuantEngineer]

I have created this small project just to isolate the operations of the blocks: Position Created, Position Closed, Order Created, and Order deleted....
https://fxdreema.com/shared/qgHw0tp6c

The custom code will only print the action detected by the 4 blocks at the upper part of the code to the console.

When the user creates or closes a position, either ways, the Position Created block is falsely triggered several times...

[QuantEngineer]

Here is how it looks... Very simple...

[l'andorrà]

The admin said that the ticket number in MQ5 is far more complicated to store than in MQ4. I've got that exact same problem and custom code will be necessary to it, but I'm still struggling on my own. I hope the admin can take a look at this thread and give us a hand.

[OntradingX]

@l-andorrà
What makes me sad is that before the data kidnapping that the admin mentioned everything worked normally, I'm afraid that most of my projects are damaged, this is causing me huge losses because I made some robots for other people and after I updated this month most of them showed some strange behavior, imagine the trouble I'm having with all these bugs. It's been a horrible experience not having these issues resolved.

[OntradingX]

@fxDreema Please at least let us know if you are trying to resolve it. Being without answers is worse than not having the solution to the problems.

[fxDreema]

@OntradingX said in Position Created block with failure.:

@fxDreema Please at least let us know if you are trying to resolve it. Being without answers is worse than not having the solution to the problems.

Yes, I started investigating this bug. It's a little bit strange situation and it will take some time, because the problem happens in a relatively large class that I wrote before for detecting Trade events, and I have to remind myself how all of this worked.

Otherwise the problem happens when the pending order and stop-loss of the position are very close to each other (they can be different). Group numbers doesn't matter.

I also have a message "Positions order mismatch", which basically means "I don't know what kind of event is this, something is off".

I'm not sure, but I think this bug is not related to my latest code changes, I think this one is an old bug that you just discovered.

[QuantEngineer]

I did 1 custom blocks to fix the issue of detecting a new position. I will share it here for you and others who might be facing the same problem.
Usage: Place the custom blocks before the FX Dreema Position Created Block, like this

The first block is called "is position created", can be done in 3 steps, here they are

[fxDreema]

I think I fixed the problem, and the good thing is that now I don't expect something else to break because of this. As I mentioned, I have this class to detect Trade events, and there was a place in this class where I just printed some message instead of trying to detect anything, it was kinda unfinished. But it was unfinished, because I didn't even expect to ever reach this place. Well, I guess in MQL5 every strange and unexpected situation is possible.

And the issue was that while the pending order is triggered at the same time when SL of the position is triggered, my Trade-detecting class detected this as a single event (instead of two), and not just any event, but one that it could not resolve.

Now I have to fix the situations when I try to open two pending orders at the same price, or to create two positions initially. These situations doesn't work.

@QuantEngineer Damn, you have so many custom blocks, you have like another EA builder.