Skip to content

Conversation

@pnrgenc
Copy link
Member

@pnrgenc pnrgenc commented Nov 6, 2025

timestamps were being adjusted twice (once via moment.tz(timezone) and once again using utcOffset) This caused a double shift in date boundaries.
Now the logic ensures only one correction is applied:

  • If a timezone is provided, only timezone-based conversion (moment.tz) is used.
  • If only an offset is provided, offset-based correction is applied

This can be also observed in the formulas or retention pages in the UI. Select the date range January 1, 2024 - January 30, 2024 and check the values ​​in the daily bucket.

timestamps were being adjusted twice (once via moment.tz(timezone)
and once again using utcOffset) This caused a double shift in date
boundaries.
Now the logic ensures only one correction is applied:
- If a timezone is provided, only timezone-based conversion (moment.tz) is used.
- If only an offset is provided, offset-based correction is applied

This can be also observed in the formulas or retention pages in the UI. Select the date range `January 1, 2024 - January 30, 2024` and check the values ​​in the daily bucket.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants