See attached.
The first part, if it hooks up, will utilise 100% - but it has to hook up, restarting it several times it will usually get it to hookup, if it doesnt it will trundel along at only 5% CPU usuage, similar to the second part (which I have never seen hookup and use 100%)
Perhaps its the same issue - hooking up - for both parts. I might get it to hook up in the first stage with 100% CPU usuage by restartying it until it does, but I dont have the same workaround option if if fails to hookup to 100% CPU usage in the second half.
In its present form it reneders the Custom Projects null and void. With WF in the process tree, you cannot leave it alone to run for any lenght of time as it will inneviatably run into this bug.
Status changed from New to Fixed
Average CPU usage during these first 8 minutes is around 90%. After that, whilst completing the remaining ~400 steps CPU usage averages only around 3 to 5%.
Is this normal behavior / to be expected?