Posted 9 September 2021, 2:31 pm EST
Using AR 15.1 If a report has a sub report and that sub report encounters a error it seems to hang the report engine at 100% cpu rather than reporting the error, the report cannot be cancelled either.
I have attached an simple repro example report with sub report containing a sql statement that will cause an error: