Ok, I got the error message and it appears that it happens when the block is moved around and then dropped on its initial position. That error message appears, but there is no error actually. I will check why that happens and fix it. For now if anyone sees this error, just ignore it... or click on it to disappear.
So if this error appears, after reload of fxDreema does the block still exist?
@drayzen Cross Width is something stupid. In the early times I was adding features here and there without too much thinking. This feature (or probably something similar) was requested by someone and I added it, but now I realize that it was a stupid feature. Or at least one that should probably be named differently, but I don't know how. The problem is that Cross Width is here for a long time and probably someone is using it for it's purpose, so I can't remove it like that. But it's also a very simple feature when you know how x> and x< works in this block. It only shifts the second candle that is checked, which is the previous candle by default. So if you try value 4... it's obvious that your indicator lines are very separated in the previous candles, the green line is always far above the red line. On candle 1, on candle 2, on candle 3 and on all visible candles (the gif) the green line is above the red line, so it doesn't matter what Cross Width is. But you better keep it 1 if you don't really, really need that feature. I know only 1 case where someone actually needed it 
Cross width does something else... and I don't recommend using this anyway. I keep this parameter only because it's there for a long time.
Maybe there was a crossover, but of course after that the lines were updated. At the end of the basktest you see only the final Close prices of all candles and the indicator's lines are based on these prices. If you want to see the exact moment when the Buy trade was closed and how the indicator looks at that moment, I suggest to connect that "Delay" block right after "Buy now" and check the EA in visual mode. Then add the indicator manually of course, because it doesn't automatically appear on the chart. I'm almost sure that you will see the lines crossed for a moment.
I think the problem is in the Condition block. I tried this and I get "array out of range" error. I will investigate why this happens
I don't know. I don't remember the last time I tried renko charts. But how I would check what is working and what is not - I would place some blocks here and there to print information for me and if certain information stops printing, then the problem can be located more easily.
Try this to see if the EA stops reacting at some point: 
I am always working on optimizations here and there, but this time the update failed a little bit. I tried to make it days ago, but then it failed even more, so I decided to give it more time. But obviously I didn't fixed all the issues. Especially your problem doesn't give any indications of a problem, there are no error messages. So, thank you for your good eye to see it
I think I fixed it now. Try it.
By the way I still expect problems, I see some errors in my logs, probably from other people
Yes, I was doing updates and I see that few errors happened for some people. You are obviously one of them I have some idea what could be wrong and I will check it now. You don't have to do anything with the project.
Your projects are there. Only one history point was lost - the last action that you did. I don't know exactly why, I hope that it was something that happened while I was restarting the server.
I will take a look. I uploaded some updates and the problems is most probably for this. I hope that the problem will be temporary of course
There is a block "Write to file". You can connect it after "Once per bar" (set to 1 hour) for example. A .csv file is written and the new data is appended, but I don't think that this will be a problem
What do you mean? To set specific symbol, just write it in that Symbol input field
This event uses probably the local clock and fires at a regular periods of time. It's that simple. Set the period here: 
But note that this event would not work properly in the Tester, because obviously the Tester doesn't work with the clock in realtime
@asif Give me more details. If the projects doesn't work in general, there would be waves of reports about this, so I think it could be something that now happens only to you... but I don't know what. Any error messages somewhere?
This is probably the same issue - https://fxdreema.com/forum/category/3/Bug-reports-and-fixes
I will take a look. I just uploaded some updates and this is most likely the reason.
It's not because of the size. There is an error in the update script and I need to check why it happens. I guess that you made this on the desktop version where the project's format is... old. The web version tries to update each project to the newest format, but at some point it fails.
Edit: I found the problem, I had some undefined variable in JS code By he way 218 blocks is not huge, I know projects with thousands of blocks
In the past I had another check to detect this - the EA was looking at the comment of the trade. But in MT4 and MT5 the comment was different, so I removed that check. I don't know, I may add some tolerance.