Please can you make anomaly detection take account of daylight savings changes as per the report suite settings?
Here in the UK the clocks have recently gone back 1 hour and the anomaly detection on all our hourly reports are now messed up (e.g. anomaly detection is displaying an expected value for 9am against the actual value for 8am)
This makes it pretty useless at the moment - also if we'd set up a lot of hourly alerts (as we'd been planning) I think this could have casued some chaos