InfluxDB 3 Core seems to ignore the 72-hour query time range limit?

1

Hi community,

According to the official documentation:

InfluxDB 3 Core limits query time ranges to 72 hours (both recent and historical) to ensure query performance.

However, when I run the following SQL query over a 13-day time range, I still receive complete results without any errors or truncation:

SELECT *
FROM mytable
WHERE time >= $start AND time <= $stop
ORDER BY time ASC

I’m a bit confused — does this limitation apply under certain conditions only?
Or has it been lifted/modified in the latest version?

Any clarification on how this 72-hour limit is enforced would be appreciated!

Thanks in advance :folded_hands:

2

If your query returned results for a 13-day range, it likely means that the number of Parquet files accessed did not exceed the query-file-limit (perhaps due to sparse data or fewer files being generated). So, the 72-hour limit is not a hard time-based cutoff but a file-based one (default: 432 files). See here for more InfluxDB 3 Core configuration options | InfluxDB 3 Core Documentation