Missing Latest Day Data in UTC+8 Timezone Queries on AWS Deployment

[woai3c]

Problem
I deployed Cube.js in the aws-us-east-2 region and noticed occasional missing data when querying with date ranges. For example, at UTC+8 time 2025-05-17 01:00:00, when requesting the past 7 days of data with the range [2025-05-10, 2025-05-16] (t-1 days), the response includes only 6 days of data, omitting 2025-05-16. However, when I run the same query at 2025-05-17 12:00:00 UTC+8, all 7 days of data appear. This inconsistency occurs frequently.

My questions:

1. Should I format date ranges in UTC+0 (instead of using my local UTC+8 timezone) when making requests?
2. Does the Cube.js server’s timezone configuration affect how date ranges are parsed, especially for the "latest" day of data?

I’m seeking guidance on resolving this missing latest-day data issue, as it impacts the reliability of our data queries.

[igorlukanin]

@woai3c It's hard to say what exactly is happening here without diving deeper into specifics.

when requesting the past 7 days of data with the range [2025-05-10, 2025-05-16] (t-1 days), the response includes only 6 days of data, omitting 2025-05-16

How are you passing that date range? Could you please show the exact query?

One explanation is that, if you're using the inDateRange filter, then the end of the range is NOT padded to include all hours-minutes-seconds of the day, while if you use dateRange for a time dimension, it's indeed padded: https://cube.dev/docs/product/apis-integrations/rest-api/query-format#time-dimensions-format

Another explanation would be that something is related to time zones. I'd recommend to specify time zones at all times when passing dates using the ISO 8601 format.

[igorlukanin]

Closing due to inactivity. Please feel free to reopen.