# Regression in Airtable node? **URL:** \ **Category:** Built with n8n\ **Tags:** core, airtable\ **Created:** [February 24, 2025, 8:41am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219 "2025-02-24T08:41:25Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 24, 2025, 8:41am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/1 "2025-02-24T08:41:25Z")
Hi there I do update my n8n instance weekly on sunday and yesterday updated to 1.79.3 and some workflow generated errors after this update. I think there is a bug with airtable node breaking node item matching. Maybe related to this update : # [1.79.0](https://github.com/n8n-io/n8n/compare/n8n@1.78.0...n8n@1.79.0) (2025-02-13) ### Bug Fixes - **Airtable Node:** Use item at correct index in base/getSchema ([#13174](https://github.com/n8n-io/n8n/issues/13174)) ([f2e3586](https://github.com/n8n-io/n8n/commit/f2e35869c143d15ea79017ec103370c4aa92a92f)) Here is an example of simple workflow to show the issue. In the “Edit Fields” node, `{{ $('Yesterday').item.json.newDate }}` returns undefined while `{{ $('Yesterday').first().json.newDate }}` work. In that case I think `{{ $('Yesterday').item.json.newDate }}` should be valid ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 24, 2025, 6:48pm UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/2 "2025-02-24T18:48:30Z")
Am I alone with this ? ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 25, 2025, 7:16pm UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/3 "2025-02-25T19:16:16Z")
Sorry to insist but I am a bit surprised that nobody is worried by this artable node issue. Can someone of the team give a feedback ? ---
**Author:** ![Daniel\_Lamphere](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/daniel_lamphere/32/39212_2.png) [@Daniel\_Lamphere](https://community.n8n.io/u/Daniel_Lamphere)\ **Post date:** [February 27, 2025, 7:47am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/4 "2025-02-27T07:47:34Z")
I’m not sure this is an air table issue. .first() is a perfectly valid syntax and sometimes preferred for pointing to the first item in an execution. ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 27, 2025, 7:59am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/5 "2025-02-27T07:59:01Z")
Yes but sometimes you don’t want the first item but the matching item. That was working previously and stopped working in recent version @Daniel_Lamphere ---
**Author:** ![Daniel\_Lamphere](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/daniel_lamphere/32/39212_2.png) [@Daniel\_Lamphere](https://community.n8n.io/u/Daniel_Lamphere)\ **Post date:** [February 27, 2025, 8:02am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/6 "2025-02-27T08:02:02Z")
hmmm maybe try aggregating the results from air table, and then either split out, or loop over the array ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 27, 2025, 9:06am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/7 "2025-02-27T09:06:01Z")
Thanks but I am not looking for a workaround. I am reporting a regression on something that work before and was broken recently ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [February 27, 2025, 9:34am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/8 "2025-02-27T09:34:09Z")
This regression really impacted different production workflows. nobody from the team @Jon ? ---
**Author:** ![Jon](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jon/32/40174_2.png) [@Jon](https://community.n8n.io/u/Jon)\ **Post date:** [February 28, 2025, 1:48pm UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/9 "2025-02-28T13:48:27Z")
Hey @Valerian_Lebert, We did a `1.79.4` release last Friday that should fix, It should also be resolved in 1.80 and 1.81 if you wanted to try one of the more recent releases as well. ---
**Author:** ![Valerian\_Lebert](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/valerian_lebert/32/13683_2.png) [@Valerian\_Lebert](https://community.n8n.io/u/Valerian_Lebert)\ **Post date:** [March 3, 2025, 10:08am UTC](https://community.n8n.io/t/regression-in-airtable-node/81219/10 "2025-03-03T10:08:32Z")
Problem solved