Errors from strategy template

Well things have got even stranger. I decided to delete the two custom blocks that had two periods in them. I then deleted them out of the random groups. I then loaded the strategy template up, clicked on 'use existing block/group' when prompted and resaved as a new file. Loaded this into the builder for the custom project and still getting the #Period2# error. Have no idea where I can go from here. All new files attached.

Voted for this task.

Hi SQ. Just hypothesising about what this could be. There are a couple of MACD conditions remaining in the latest file. The inputs for both of these are classed as integers and so you have to build integer parameters for these. However, they are actually periods for the two moving averages - could it be that the error is caused from SQ needing period parameter types?

Just tried deleting those two MACD conditions from the random group and that didn't work - still the same error. Going to keep playing around with deleting conditions until I find the offending one(s).

I have just deleted all the conditions out of the random groups and replaced them with a few simple fixed signals and that worked fine.

Ok found the issue. It was in the "trd_ADX_rge.chgBinRis" custom block. Somehow one of the ADX period parameters had been replaced by one of the parameters from the MACD custom blocks - I DEFINITELY haven't done that manually. Corrected this and all works ok. Two main conclusions:

1. The custom block / random group feature is amazing but it is still very buggy - I've noticed a number of times when I change or delete something somewhere then something else unintended happens (like the example in this task). I haven't logged the issues because I couldn't replicate it. I think there's some serious testing/improvement that needs to happen on this new feature.

2. The log isn't detailed enough for users to be able to quickly diagnose issues. It took me over an hour this morning of trial and error - deleting each block one by one to track this down. Can we get something added to the log to state which block is causing the error? This will speed things up whilst the whole block/group feature is made more robust.

improved logging, now it indicates the custom block where the error occured and the error reason.