# Calendar component stopped working when both Start and End use no-timezone date columns from a Supabase view

**URL:** <https://community.glideapps.com/t/calendar-component-stopped-working-when-both-start-and-end-use-no-timezone-date-columns-from-a-supabase-view/86960>\
**Category:** Ask for Help\
**Created:** [April 25, 2026, 12:52am UTC](https://community.glideapps.com/t/calendar-component-stopped-working-when-both-start-and-end-use-no-timezone-date-columns-from-a-supabase-view/86960 "2026-04-25T00:52:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mateo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mateo/32/79814_2.png) [@Mateo](https://community.glideapps.com/u/Mateo)\
**Post date:** [April 25, 2026, 12:52am UTC](https://community.glideapps.com/t/calendar-component-stopped-working-when-both-start-and-end-use-no-timezone-date-columns-from-a-supabase-view/86960/1 "2026-04-25T00:52:01Z")

</div>

Hi everyone,  
I’m seeing a strange issue in Glide’s Calendar component and I’m not sure if this is a bug or an unsupported setup.

My data source is a Supabase table view connected to Glide. I think this matters because in this setup Glide can only filter/use actual Supabase columns, so I can’t solve this by switching to a Glide-computed column unless that value already exists in Supabase.

I have 4 date columns:

- `start_at` - respect timezone

- `end_at` - respect timezone

- `start_dt_no_tz` - doesnt have timezone

- `end_date_no_tz` - doesnt have timezone

The first two are normal Date & Time columns that respect time zones, so users in different time zones may see different times. The `_no_tz` columns do not respect time zones, so they show the literal same time for everyone.

Until yesterday, my Calendar component in the layout was working correctly when I mapped:

- Start time = `start_dt_no_tz`

- End time = `end_date_no_tz`

\*\*But today that stopped working.  
\*\*

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/6/563befe593a71af59e06f31b2100951147703e7b.jpeg)

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

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

**What is strange:**

- `start_dt_no_tz` works fine in the Start time field

- `end_date_no_tz` works fine if I put it in the Start time field

- the normal timezone-aware `end_at` works fine in the End time field

- the only combination that fails is:

**When I use that combination, the calendar shows nothing.**

The confusing part is that both no-timezone columns appear to be set up the same way, so if one were invalid I would expect both to fail, not only the end field.

Since this is coming from a Supabase view, I’m especially trying to understand whether Glide’s Calendar component is handling no-timezone end fields from Supabase differently than start fields, or whether this could be a recent bug/regression.

Has anyone seen this before?