Report executes once final param is entered, and UI largely freezes until it's done

Hi, I'm trying to figure out if this is normal behavior or not. Frequently, when filling out parameters on the User Console scheduling popup, the widgets inside the gray parameter area become frozen, and the Next button at the bottom of the popup is disabled, despite all parameters being specified. This happens to coincide with the report being executed, according to my Vertica query monitoring. This is concerning because it doesn't happen every time, ceteris paribus. It happens even with a fresh Ubuntu bi-server-5.4 install with default configs, etc., right out of the zip archive. I think part of the problem is our Vertica setup, because the query sometimes fails, but I'd like to understand why the report is running before I tell it to. It might make sense to do this in order to cache the report structure or something, but I would expect that the developers would naturally make this a background operation that doesn't freeze the UI.

It seems like a report should only run either at the time of a scheduled run or after I click Ok to finish scheduling a report. And in both cases, even if there are all kinds of ugly errors in the background, this should not adversely affect the UI. I would prefer even a popup saying "Something went wrong," or "By the way, we're going to go ahead and freeze the UI while we run your big report for a few minutes, for no apparent reason. Deal with it."

Can someone please elucidate this for me? And where in the github repo can I find the source for this? I'm expecting to see an AJAX call that makes the report execute when all parameters are specified.

Thanks a lot,
Alex