You have Candle High > MA+2pips. Candle High stays high until the end of the candle, it will only become higher. Your MA is set to the close price, so what happens, I guess, is that Candle High is always higher that this MA.
Try with Candle Close instead.
You also don't need this "Once per tick" block, it is used for another scenario. This block is just a filter. Your blocks are already under the "on Tick" event.
This is how it looks if I add the indicator manually, so I can see it realtime:
http://img.prntscr.com/img?url=http://i.imgur.com/NTQJkuR.png
And this is how it looks if I backtest it normally - it's the same thing, but without the manually added indicator:
http://i.imgur.com/W1M7J1G.png
So it looks that at some places the indicator is giving wrong signals while running - both buffers have the same values at the same time. Then, when the backtest ends, MetaTrader draws the indicator over the chart, but it does not have problems to draw it's lines in the past, so it looks fine. But while the action happens it's another story.
I don't know what is wrong with this indicator, but there is something...
http://img.prntscr.com/img?url=http://i.imgur.com/WCro5CG.png
This happens when I manually add the indicator right after the EA starts to run. If I add it later, on 25 march let's say, it draws everything behind correctly. I even tried with empty EA, no blocks, no indicators out of it, only the manual indicator that I add later.
MetaTrader makes the EA to run and to do it's jobs, it's not self-executable. EAs are more like instructions that you add to MetaTrader. When you close MetaTrader, EAs also die with it.
That's why you can see advertisements of VPS servers here and there. VPS is normally used to host websites, for example this website is located on a VPS server, but some brokers offer VPS servers specialized for trading. Well, I never tried this, to be honest, so I don't know what is more special. I will suggest to ask somebody else about this 
It is possible, but not in the same way. You can write the MQL4/MQL5 name of the variable in the field and it should work. You can see the name in Constants, under "MQL name"
Click on the bench icon on the lower right corner. Also, this is an input parameter that exists for all EAs.
I can see that you have "+pip" in the Adjust fields... better try something like +0.0005
There is a block "Check current unrealized profit" that calculates the profit from a group of trades, then you can put "Close trades" set for the same group
Oops, I forgot to write it here, but I changed some things. Look here: post/7973
Please, don't check the checkbox for optimization when you have Constant or Variable in there Ugly things happen because Constant and checkboxes do the same thing. And better use those checkboxes only temporarily, when you want to optimize something.
I found a problem in the block (when using group numbers > 0) and I fixed it But there are some other things as well...
Here is an example that I think it works the way you want it to work, but without your indicators: https://fxdreema.com/shared/ObCwcbazb
Note that I used two "Check..." blocks. It seems that I make this block so the yellow output is "otherwise" to the orange output and works every time when the orange output is not active, including the times when the orange output is inactive because of the "Pass once per trade" parameter. Maybe I should make is work like the EA that I'm showing now, like 2 blocks in 1, I don't know.
In block 3 I used two group numbers, you will see this value - 0,1
It's important that block 2 has lower ID number than block 3 here, because I want block 3 to run after block 2.
I will skip your project, it has indicators that I don't have and you also use custom input parameters. Also "not executing properly" means nothing to me, it's the same as "I have a problem" without actually explaining the problem.
The block is working otherwise, here is an example: https://fxdreema.com/shared/jxpoSVVze
and the result it this:
http://img.prntscr.com/img?url=http://i.imgur.com/KgHE7CF.png
So I don't know, maybe something with Group numbers. If possible, don't use multiple groups. Everything that makes things more complex is not a good idea
Here are all the built-in MQL4 functions designed to create, delete, modify and get information from trades and pending orders. You can see OrderMagicNumber(), OrderStopLoss(), OrderLots()... there is nothing special for the chart where the trade/order is created. Instead, Magic Number is normally used to distinguish trades from different EAs. But when you put them manually, it is 0.
More than that, when you create a trade in one chart, it immediately appear on the other charts from the same symbol. I will say this again, when you send request to the broker to create a new trade, no information about the current chart is sent (who knows really?) and no information about this chart can be get then, when you read properties of trades and orders. Simply because there is no such property like OrderChartID().
Anyway, the only thing that pops in my mind is the Comment property. But you need to remember to always write something there... this is not very intuitive.
Looking at these screenshots, can you tell me what can be wrong in block 4? It's not a bug actually, but it's something that I'm probably going to fix.
I test indicators with the block called "Indicator tester". It's somewhere on the top of the list. For this indicator it draws exactly what I expect:
Of course, when I use Candle ID = 0 and the color turns into green or red, it sometimes changes it's decision in the middle of the candle, but this is so expected from custom indicators.
I wrote this funny text here, hopefully you will get it: https://fxdreema.com/documentation/gett ... c%20number
This is again about magic number, but when you use it in fxDreema: https://fxdreema.com/documentation/proj ... d%20groups
In short, you can use Magic Number to make trades and orders to appear as they belong to different groups, but the chart itself is not important. You can actually create GBPUSD trades from EA running in EURUSD chart, for example. The magic number is what allows you to group them, when their symbol name and type (buy, sell) is not enough.
About your EA - block 7 and block 8 are not used correctly. I wrote about this 100s of times here and there, so I'm just tired to do it again. Read this if you want: https://fxdreema.com/demo/mt4-loop-how-it-works
Blocks 9, 1, 3 and 5 are filters. You also have the same filters in 11, 2, 4 and 8, so 9, 1, 3 and 5 are not needed for the work of 11, 2, 4 and 8.
I'm not sure what are you trying to do, but I guess the answer is yes 
"AND" block is not needed.
You have "Delete pending orders" set to delete all pending orders with magic number 1412 (MagicStart+Group). I don't know where your pending orders comes from, probably another EA. In any case, make sure that magic numbers match.
Here is a simple example of creating multiple pending orders and then delete them using "Delete pending orders":
https://fxdreema.com/shared/okJGnBp8e
It works for me:
http://img.prntscr.com/img?url=http://i.imgur.com/GChz1bF.png
The problem is in this input:
http://img.prntscr.com/img?url=http://i.imgur.com/BPYtVCt.png
While everything is fine inside the indicator itself, the EA does not know about this datatype that is defined in the indicator ENUM_PRICE, it also does not know variable/constant with name PRICE__MEDIAN. This enumeration is defined and used in the indicator, but the EA does not have access to it, so from the EA it looks like something undefined.
I will suggest to change the datatype from ENUM_PRICE to int and the value from PRICE__MEDIAN to 0.
You can see where possible values of that enumeration are defined up there - PRICE__MEDIAN, PRICE__OPEN, PRICE__CLOSE.... as a numbers they are 0, 1, 2, 3, 4, 5, 6 and 7.
Enumerations are good because when you add indicator to the chart, you can select from all possible values in that enumeration. There is no need for you to know what value to add - 0, 1, 2, 3... this is hard to remember. So enumerations are way to make input parameters more intuitive. But when when you use that indicator in an EA, they does not seem to work the same way
I removed that cache now, otherwise I need to make the code even more complex, which is something I don't like. So I don't know, maybe I will turn it on again if someone decide that the block runs slowly.
Anyway, does it work now? I have blue lines here and there, but I have no idea what should I see