We aren't planning to release today. Probably Monday.
However, I am afraid Boris was a bit misleading. He fixed the error handling, not the actual error which will need more investigation.
Not sure at this moment, maybe it is a race condition on our side and maybe the process is just failing because of not enough resources.
In that case, you should limit the parallelization on your side.
In case the problem is persistent and you need to recover please use KillRunningJsReportProcesses and restart.
var rs = new LocalReporting()
I also recommend trying using the "AsWebServer" strategy.
So far it looks like we have never-ending problems with "AsUtility" and maybe the "AsWebServer" will work better for you.