Reports
Aggregate date ranges and timezones
Set calendar periods and custom dates, check timezone boundaries, and understand why Refresh keeps the saved reporting window.
Aggregate dates filter the Report's recorded submission time in the timezone chosen during creation. They do not filter a date entered inside an answer.
Set the reporting period
- In Create report aggregate, choose Date range.
- Confirm Timezone. Use a valid timezone such as
America/ChicagoorUTC; do not assume the suggested value is your device's timezone. - For Custom range, choose Start date and End date.
- Review the matching Report preview before creating the aggregate.
| Range | Calendar period |
|---|---|
| Last week | The previous complete Sunday-through-Saturday week. |
| Week to date | The current week, starting Sunday. |
| Last month | The previous complete calendar month. |
| Month to date | The current calendar month. |
| Last year | The previous complete calendar year. |
| Year to date | The current calendar year. |
| Custom range | Your selected start and end dates, including the end date. |
Boundaries follow the selected timezone, including daylight-saving changes. A custom end date must be on or after the start date. The whole selected range cannot exceed one calendar year.
What Refresh changes
The chosen calendar window is saved when the aggregate is created. Refresh does not move it into a new week, month, or year.
For a “to date” range, each generation can extend the cutoff up to its request time, within that saved period. Once the period ends, the cutoff stops at its saved end. For example, an October Month to date aggregate refreshed in November still covers October.
Last-period and custom ranges retain their saved boundaries. Refresh can pick up additional eligible Reports within those boundaries, but does not expand the range or change its timezone. Create a new aggregate for a different period.
If the preview is empty or invalid
Check the timezone, source, Match, people selection, and dates together. A Report close to midnight may fall on a different local date than expected. Correct an invalid timezone or reversed/oversized custom range, then wait for the updated preview. Do not treat a failed preview as zero matching Reports.
See generation and source changes before rebuilding an existing snapshot.