Wrong time range inside the report

Alright, so we tried it on a fresh CME 2.1 p24 and were not able to reproduce it. Everything worked as expected. So it doesn’t seem like it’s a bug for now.

We’re well into the land of speculation now, but:

Could it be some kind of time-zone issue? Server time being off? Could it be a wrongly set date for the change in Daylight Saving time (happened in the US in the night from March 11 to 12, and in Europe will happen March 25 to 26)? Interesting that your time period happens to be right in between those two…

What happens if you do it for “yesterday”, meaning March 20?

1 Like