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

**URL:** <https://community.influxdata.com/t/influxdb-3-core-seems-to-ignore-the-72-hour-query-time-range-limit/57443>\
**Category:** Systems\
**Created:** [June 17, 2025, 8:22am UTC](https://community.influxdata.com/t/influxdb-3-core-seems-to-ignore-the-72-hour-query-time-range-limit/57443 "2025-06-17T08:22:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaouai](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/shaouai/32/17297_2.png) [@shaouai](https://community.influxdata.com/u/shaouai)\
**Post date:** [June 17, 2025, 8:22am UTC](https://community.influxdata.com/t/influxdb-3-core-seems-to-ignore-the-72-hour-query-time-range-limit/57443/1 "2025-06-17T08:22:39Z")

</div>

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:

```sql
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 🙏

---

<div class="post-metadata">

**Author:** ![suyash](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/suyash/32/15791_2.png) [@suyash](https://community.influxdata.com/u/suyash)\
**Post date:** [June 17, 2025, 10:19am UTC](https://community.influxdata.com/t/influxdb-3-core-seems-to-ignore-the-72-hour-query-time-range-limit/57443/2 "2025-06-17T10:19:33Z")

</div>

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](https://docs.influxdata.com/influxdb3/core/reference/config-options/#query-file-limit)