Genesys Cloud – Calendar-month alignment for detail exports
| Type | Impact | Action required | Audience | Community link | Aha! link | Announced on (YYYY-MM-DD) | Planned effective date (YYYY-MM-DD) |
|---|---|---|---|---|---|---|---|
| UI/UX | Medium | Awareness Only | Admin | — | — | 2026-10-12 | - |
In a future release, Genesys Cloud will align monthly detail exports with calendar-month boundaries based on the timezone specified in the export request. When users select monthly (P1M) granularity, Genesys Cloud will group data from the first day of one month to the first day of the next month instead of using intervals that can result in misaligned or duplicate rows. This change will also handle partial months correctly when the selected date range begins or ends within a month.
What’s changing
- Calendar-month boundaries – Monthly detail exports will align data with calendar months, from the first day of one month to the first day of the next.
- Timezone-based grouping – Genesys Cloud will calculate monthly boundaries using the timezone specified in the export request, including for non-UTC timezones.
- Partial-month handling – Detail exports will correctly represent partial months at the beginning or end of the selected date range without creating duplicate rows.
- CSV and PDF exports – The updated monthly grouping will apply to detail exports in CSV and PDF formats.
Why this matters
Users who rely on monthly detail exports for reporting need each row to represent the expected calendar month. This change corrects cases where monthly data could be misaligned or duplicated, particularly when using non-UTC timezones. As a result, exported data will more consistently match the calendar periods that users select for reporting.
[NEXT] Was this article helpful?
Get user feedback about articles.