I'm not sure what you mean. If you're using a rollup in the PointValueQuery, then you aren't being given a time with the value in the callback. If you've used a rollup of `ALL`

then you would be presented with the entire statistics object for the period, which would have functions for both `getPeriodStartTime()`

and `getPeriodEndTime()`

As far as how the periods get determined, it is not like an Excel Report where the rollup of 1 hour will expand the queried period to a rollup boundary in time (so 60 minutes != 1 hour for rollup logic). Instead, periods will begin at the start time, and the last period will be smaller than the rollup period if the overall period doesn't evenly divide.

]]>So what I meant was that I had assumed that if I say "give me a 1 hour sum rollup" than no matter what Mango would be looking for start and end of an hour period, quantized to the top of an hour. This was my assumption. I suppose what I have found however, and what your alluding to, is that, using the PointValueQuery function, a one hour rollup starts based on whatever starting time I provide correct? So if I pass March 6 2019 02:34:00 to the function, a 1 hour rollup will be 02:34-03:34, 03:34-04:34 etc. Is that correct?

]]>