# Airtable and Glide connection

**URL:** <https://community.glideapps.com/t/airtable-and-glide-connection/83801>\
**Category:** Ask for Help\
**Created:** [August 13, 2025, 8:28am UTC](https://community.glideapps.com/t/airtable-and-glide-connection/83801 "2025-08-13T08:28:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![christinakrogh](https://avatars.discourse-cdn.com/v4/letter/c/13edae/32.png) [@christinakrogh](https://community.glideapps.com/u/christinakrogh)\
**Post date:** [August 13, 2025, 8:28am UTC](https://community.glideapps.com/t/airtable-and-glide-connection/83801/1 "2025-08-13T08:28:37Z")

</div>

Hi, I’ve been using Glide with an Airtable base for over a year, and my Calendar component has always worked fine. It uses two Airtable date fields (Arrival date as start, Departure date as end).

A few days ago, without me changing anything in Airtable or Glide, the calendar suddenly started showing the same date (13 August 2025) for all events. In Airtable, the dates are all correct and different for each record. The fields are true Date type (not text or formulas).

I’ve tried:

- Reloading data in Glide

- Disconnecting and reconnecting Airtable

- Creating a new app

- Creating a new Airtable base

- Double-checking field types

The problem persists — it’s as if Glide is reading only one date and applying it to all items.

Has anyone else experienced this recently? Is this a known bug with Airtable date fields?

**What I see in Glide**

 ![Screenshot 2025-08-13 alle 10.15.33](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/1/e/1e69bd17b55141708ea85461582abcba62985d6c.png)

 ![Screenshot 2025-08-13 alle 10.11.38](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/1/8120856cba7b204816ceae582e8aceee1e6085cd.png)

**What I see in Airtable**

 ![Screenshot 2025-08-13 alle 10.11.55](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/a/daa100ad8967af5331d5363bf23f3ff78d84f1e8.jpeg)

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 13, 2025, 8:36am UTC](https://community.glideapps.com/t/airtable-and-glide-connection/83801/2 "2025-08-13T08:36:57Z")

</div>

This issue has been reported to Glide Engineering, and a fix is in the works. At this stage, no ETA on when the fix will be deployed.

---

<div class="post-metadata">

**Author:** ![christinakrogh](https://avatars.discourse-cdn.com/v4/letter/c/13edae/32.png) [@christinakrogh](https://community.glideapps.com/u/christinakrogh)\
**Post date:** [August 13, 2025, 8:39am UTC](https://community.glideapps.com/t/airtable-and-glide-connection/83801/3 "2025-08-13T08:39:43Z")

</div>

Ha okay, I did find a fix though! In the data field in Airtable I added that it should show also the time and that actually worked, so now I see this in my calendar:

 ![Screenshot 2025-08-13 alle 10.38.21](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/e/ee3cfedb327a634238ef8adfc4cbec1ca43f5043.png)

But thank you for the quick answer!!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 13, 2025, 8:42am UTC](https://community.glideapps.com/t/airtable-and-glide-connection/83801/4 "2025-08-13T08:42:16Z")

</div>

> [@christinakrogh](#):
>
> Ha okay, I did find a fix though! In the data field in Airtable I added that it should show also the time and that actually worked, so now I see this in my calendar:

Yes, that actually makes sense. It seems that a date value like `YYYY-MM-DD` is misinterpreted as the current date, but a date with a time (`YYYY-MM-DDTHH:MM:SSZ`) is interpreted correctly.