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

Ask for Help
1

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
image2468×1544 170 KB

image
image2458×1530 169 KB

image
image1470×1308 121 KB

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:

    • Start time = start_dt_no_tz

    • End time = end_date_no_tz

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?