@rld51251 Here you can find some ideas?
https://fxdreema.com/forum/topic/5071/total-profit-of-current-orders-in-pip/2
https://fxdreema.com/forum/topic/8710/close-all-when-total-profits-reach
@rld51251 Here you can find some ideas?
https://fxdreema.com/forum/topic/5071/total-profit-of-current-orders-in-pip/2
https://fxdreema.com/forum/topic/8710/close-all-when-total-profits-reach
@agitins Disconnect blocks 15 and 16. Then disconnect blocks 14 and 10. Then use a 'Pass' block not connected to any other block and finally connect block 14 below it.
@julianrbach Not directly. You can try something like this:

In this example I'm comparing the open price of yesterday's Bull HA daily candle with today's open price. If this condition is true, any other condition connected below this one will be checked.
@deiby De acuerdo. Si te parece, lo centramos todo en este hilo. ¿De acuerdo? ¿Serías tan amable de compartir tu proyecto para echarle un vistazo?
@malospelos In that case you don't need to draw any line at all. You just need to take those values into variables and then compare the price level to them.
@malospelos Are those lines created at any candle's high/low prices?
@jwabe This same question was asked in another thread. Please don't duplicate threads.
@alfredinho50 This is stuff for real programmers. Considering it comes from a custom indicator, I guess you will need some custom code, but I'm not sure. Maybe roar or miro could help.
@ttu22 No, it probably is because the opening conditions are still active and the EA is not programmed to recognize that it shouldn't open more trades.
@timoglock You are asking for the Holy Grial, my friend.
I don't think anyone having such a successful EA would share it here. 
@zarbitz You can try this, but there is never a guarantee that your requirements will allways be executed:

Otherwise, try the 'on timer' tab, but I'm not sure it would be more efficient.
@jwabe Remove the 'once per trade' block and specify cnadle ID 1 on both operands of the condition block.
@abderrahman This is stuff for real programmers but I guess the problem is that the custom indicator's buffers are not correctly identified by fxDreema. Remove it from your custom indicator's pool and follow these tutorials:
https://fxdreema.com/forum/topic/4208/tutorial-06-my-indicators-in-fxdreema
https://fxdreema.com/forum/topic/9105/tutorial-working-with-ex4-ex5-indicator-file
@profaalaa Yes, it can be done, but you will need a specific structure for it: importing the custom indicator, checking the buffers, etc. It is not a simplt 2 blocks solution if that is what you are looking for.
¿Este problema está relacionado con el de tu otro hilo? Lo digo para no duplicar respuestas.