# Date comparisons involving today do not work correctly in Query filters

**URL:** <https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236>\
**Category:** Report a Bug\
**Created:** [June 2, 2026, 8:15am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236 "2026-06-02T08:15:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![insect\_yoo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/insect_yoo/32/94527_2.png) [@insect\_yoo](https://community.glideapps.com/u/insect_yoo)\
**Post date:** [June 2, 2026, 8:15am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236/1 "2026-06-02T08:15:35Z")

</div>

My `Deadline` column is in a Glide Big Table, and the Query column is in a regular Glide Table.  
I’m trying to query rows where the deadline is today. My timezone is KST (UTC+9).  
Today is June 2, 2026.

**[Screenshot 1 - Tasks table]**

 ![Deadline1](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/1/31806584819bcab21d4c37de0217b195b21b1fe5.png)  
The Tasks table has 5 rows.  
June 2 rows are #4 and #5, June 3 is #3.

**[Screenshot 2 - Attempt 1]**

 ![Deadline2](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/9/09c7d2e767d9f9227f4155c10b97fd5766083985.png)  
I created a Query column with filter `Deadline > is within > today`.  
Expected: June 2 rows.

**[Screenshot 3 - Attempt 1 result]**

 ![Deadline3](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/d/ad24239f754025fbff7a3a21301f10e0d0531c18.png)

The result returns June 3 (06-03) instead of June 2. Wrong result.

**[Screenshot 4 - Attempt 2]**

 ![Deadline4](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/0/809f5cae1e7a504de63b0c5ecd4899ba1e326285.png)

To work around this, I created an ITE column: `IF Deadline is within today → TRUE, ELSE → FALSE`.  
June 2 rows (#4, #5) correctly show TRUE, June 3 row (#3) shows FALSE.

**[Screenshot 5 - Attempt 3]**

 ![Deadline5](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/0/0012968b4d9129ca4984811c498b9024342d3db1.png)

I then used this ITE result in a Query filter (`Deadline ITE > is checked`).  
But it still returns June 3 — same wrong result.

It seems like `is within today` is calculated based on UTC, not the user’s local timezone.  
For KST users (UTC+9), this causes tomorrow’s date to match instead of today’s.

Tested at: June 2, 2026, 4:56 PM KST (UTC: June 2, 07:56 AM)

I believe this might be a new bug. If I recall correctly, this was working fine a few days ago and I don’t remember having this issue before.

* * *

[Additional Issue]

I have the same issue in a different context. I have a table with `Start` and `End` date columns, and I’m trying to query rows where today falls within the date range.

I built a chain of ITE columns:

- **ITE 1:** IF Start is on or before today → return Start (confirms the row has already started)

_[Screenshot A - ITE 1 configuration]_

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/b/7bf182eed99fca2c7f3e14097e7e307b44f443cb.png)

- **ITE 2:** IF ITE 1 is not empty → return End (gets the end date)

_[Screenshot B - ITE 2 configuration]_

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/d/fdb6644bcedf0408de595d709e93073f3f72193f.png)

- **ITE 3:** IF ITE 2 is on or after today → true (confirms it hasn’t ended yet)

_[Screenshot C - ITE 3 configuration]_

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/b/6bd9775931c2e2ab984904fcc5c24071b82eeb46.png)

In the table view, ITE 3 correctly shows TRUE for rows where today falls within the range (e.g. May 29 ~ June 5).

_[Screenshot D - Table view showing ITE 1, 2, 3 results]_

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/3/83f8c85e52732e4d840af3ed1d45e394f2f81a34.png)

However, when I use `ITE 3 is checked` as a Query filter, it returns no results — completely ignoring the TRUE values.

_[Screenshot E - Query filter configuration, Empty query result]_

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/3/f331b8ea10e8efdd83cfb86f5518ad939bf45287.png)

Same underlying issue: The root cause appears to be that date comparisons involving `today` do not work correctly in Glide.

---

<div class="post-metadata">

**Author:** ![insect\_yoo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/insect_yoo/32/94527_2.png) [@insect\_yoo](https://community.glideapps.com/u/insect_yoo)\
**Post date:** [June 4, 2026, 8:57am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236/2 "2026-06-04T08:57:05Z")

</div>

Still no response after 2 days. Any update on this?

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [June 13, 2026, 12:53am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236/3 "2026-06-13T00:53:12Z")

</div>

The “within today” query has always been a bit buggy…especially when dealing with timezones. I like to convert my dates to integers to compare. Works much more reliably. See here:

[![](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/f/ef5ddcc34a48d44cc7c9536d280afc0b98002149.jpeg "Glide: Calculate Dates") ](https://www.youtube.com/watch?v=DkcLP9ZI6V4)

---

<div class="post-metadata">

**Author:** ![insect\_yoo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/insect_yoo/32/94527_2.png) [@insect\_yoo](https://community.glideapps.com/u/insect_yoo)\
**Post date:** [June 13, 2026, 6:08am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236/4 "2026-06-13T06:08:02Z")

</div>

Thank you, Robert. I solved the problem by adding 9 hours to the UTC timeline to create Seoul/Korea time.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [June 20, 2026, 6:08am UTC](https://community.glideapps.com/t/date-comparisons-involving-today-do-not-work-correctly-in-query-filters/87236/5 "2026-06-20T06:08:49Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
