-
I’m facing an issue where Zapier does not reflect new Airtable fields and new records, even though they are correctly visible in Airtable
-
I added a new column (Language) in Airtable, coming from a synced table / lookup, and I can see it correctly populated in Airtable
-
After adding the column, I refreshed the synced table, re-synced it, and confirmed the field is visible and filled in Airtable
-
However, in Zapier, this new column does not appear in the trigger output, and any Path conditions based on this field do not work
-
I also notice that when testing the Airtable trigger from step 1, Zapier only returns old records (stopping around 20 November) and does not include more recent records that exist in the table
-
I already tried refreshing fields in Zapier, re-testing the trigger, removing and re-adding the Airtable table and view, and rebuilding the Path filters, but the issue persists
-
As a result, Zapier shows “missing field mapping” for the Language field in the Path conditions, even though the field clearly exists and is populated in Airtable
-
I’m trying to understand why Zapier seems stuck on an old schema / old dataset, and how to force it to fully refresh both the table structure and the latest records from Airtable
