Skip to:
A hard-coded timestamp has snuck into one of the sub-selects in the report query where the START_TIME parameter should be used instead.
Fix pushed to 1.8 in commit 70783f25d4e78bd2b12c9a997f1a41c717c545ea and cherry-picked to master in commit f9ae6c60c04c3eaf905768fbf5236ae1ee17bb68.
Easy fix, I've got it.
A hard-coded timestamp has snuck into one of the sub-selects in the report query where the START_TIME parameter should be used instead.