Airtable Create Record module does not show newly added fields, but a new module does

Questions
1

:bullseye: What is your goal?

Understand why an existing Airtable Create a Record module does not show newly added Airtable fields, while a completely new module connected to the same base/table does show them.

:thinking: What is the problem & what have you tried?

Hi,

I’m running into an issue with an Airtable “Create a Record” module in Make.

Setup:

  • App: Airtable
  • Module: Create a Record
  • Existing Make scenario
  • Existing Airtable base/table
  • I added new fields to the Airtable table
  • I want to map those new fields in the existing Make module
  • Input contains data for new fields, visible in run data

Problem:
The newly added Airtable fields do not appear in the existing Create a Record module.

What I already tried:

  • Refreshing the module fields/form
  • Switching to another Airtable table and switching back
  • Saving the scenario
  • Leaving and reopening the scenario
  • Refreshing the browser page
  • Clearing/deleting browser page data
  • Cloning the existing Airtable Create a Record module

Result:
None of those made the new fields appear in the existing module or in the cloned module.

However:
If I create a completely new Airtable Create a Record module and select the same connection, base, and table, the new Airtable fields do appear correctly.

So it looks like the existing module has stale cached schema/form metadata, and cloning seems to copy that stale metadata as well.

Questions:

  1. Is this expected behavior or a known limitation with Airtable module metadata caching?
  2. Is recreating the Airtable module the recommended fix?
  3. Is there any way to force a full schema refresh on an existing Airtable module without rebuilding it?
  4. Are there known cases where a cloned module keeps stale metadata even though a newly created module works?

For now I will rebuild the module manually, but I’d like to know whether there is a cleaner way to refresh the existing module because remapping many fields is error-prone.

Thanks.

:clipboard: Error messages or input/output bundles

No error message.

The issue is that the newly added Airtable fields are missing from the existing Airtable Create a Record module’s field mapping UI.

Expected:
New Airtable fields should appear after refreshing/reloading the module.

Actual:
New fields do not appear in the existing module or in a cloned copy.

Control test:
A completely new Airtable Create a Record module connected to the same connection/base/table does show the new fields correctly.

3

Hello,

I can confirm this is not just on your account - I reported the same issue a few days ago. Hopefully there will be a quick fix.

As a workaround, you can copy the module, open via any text editor,then add the missing field by its ID under:

root.subflows[0].flow[0].metadata.restore.expect.table.nested[0].spec[X].name

then paste it back.

Or use Make DevTools to replace module.

Have a nice day,
Michal

4

Thank you for confirming, and also for the tip, that can be useful.

My airtable has a lot of fields, so it’s just a hassle to remap them all. Let’s hope they can find the issue.

Cheers

5

I also have the same issue, and agree it can be time-consuming to re-map.
Hope this can get fixed as it’s worked well before.