Well, I don't know this particular indicator, but for any custom indicator you can first check if it's buffers are actually giving you normal values using "Indicator tester" block. Then, when you know that buffer X is working and when you know how it's working, you can use it.
Block "AND" is not needed at all.
This value of "0" for "Adjust" is... just clear this value, this field is not used like this. Maybe you should read the description of "Condition" block.
Try this:
"Check current unrealized profit" -> "Close trades"
The crossover in "Condition" block does not produce one-time signals, the block will pass until there is a visible crossover for the candle, until the candle closes. So you should control trades with other blocks. For example, if you put "Once per bar" before that Condition, it will give you some result. If you put the same block after the Condition, the result will be different.
If something is wrong with the count of trades/orders in MT4, then the reason is most probably in your project logic. In this case I can help if you show me your project. If the project is fine and there are problems, then it's a bug and I want to fix it.
In case of MT5... weird things happen there, but again - show me the project, it's easier if I can see the situation, because I have no crystal ball to detect problems.
So where was the problem? And what MetaTrader is this 4 or 5? Because I know that MT5 sometimes does weird things because of it's nature - it does not wait for it's own local database to be updated before going to do something else. For example, when you create a new position with OrderSend() and the response from the server for this operation is positive, and then you load (select) the newly created position, for some milliseconds it's attributes return 0 (open price, stop-loss...).
I don't have any problems with this:
https://fxdreema.com/shared/xrJfkmeDb
http://prntscr.com/5i53j3
Note that all trading blocks are creating trades/orders when they are executed, they don't have internal limits. If you run these blocks 1 time, they will create whatever they are set up to create. If you run them 2 times - they will create whatever they are set up to create X2, and so on...
I guess that the problem is in the "limit" block/s above the trading block.
Oh boy... I was really fixed that and I was also uploaded it, but forgot to replace the file on the server. Stupid me 
Weird, I believe I fixed that already, but it looks that I'm wrong. I will check what is going on here and I will fix it in minutes with a new build.
No, this is how MetaTrader works and call things. They have 3 types of programs - Expert Advisors, Scripts and Indicators 
Is this the desktop version? Can you try to download it again? Sometimes I reupload the same version when people report problems in the next 2-3 days
Scripts run once when you manually run them, then they automatically exit. Experts are working until you remove them, they do something on every tick. If this is what you need - make an expert advisor.
Put this under "on Start": Pass -> Modify stops of trades
Then for "Modify stops of trades" change "Group mode" (click on "Origin of trades" first) to "Manually opened"
You can use the Adjust box to make simple calculations over operands in the Condition block. Just click on "Adjust" and then write there something like *2 or -10 or +20 or *1/100 or something else. Everything you write will be included into the final code, so you can also use functions and variables.
Or maybe you want to put multiple pending orders at some distance from each other? In this case use those blocks that contain "grid" in their names, you will see them.
Or try "Round numbers detector". This block is interesting, but better read it's description.
No pending order -> Buy/Sell pending order
For such things there are indicators, but you can use Condition anyway. Just remember to not use == when you compare prices. The chance to detect two prices that are exactly the same at the same time when ticks are jumping around and the broker have 5 digits is pretty low.
Then just look at what you have - two conditions with the same left and right operands, but using different comparison sign. There is just no way to have both Condition block right at the same time, one of them is always false, they are the opposite of each other.
You can get the profit of the last closed trade, here is how: https://fxdreema.com/shared/8rgo60N1d
Oooops again... I missed something, I will reupload it after a while.
Long story short - not possible in the backtester, because the Timer event does not work there - there is no way to detect exact time when you only have irregular ticks events.