Setup incomplete” issue in CMS Bridge.

CMS Bridge
1

Hi, I’m stuck with a persistent “Setup incomplete” issue in CMS Bridge.

Summary:
• One Airtable linked field briefly showed setup incomplete
• After that, CMS Bridge started resolving all reference fields through the same source
• I recreated linked fields, duplicated bridges, reconnected tokens — no change
• Even brand-new linked fields are ignored
• Now multiple bridges show Setup incomplete

This looks like a cached Airtable schema issue.
Has anyone from the CMS Bridge team seen this before or can reset the schema cache for a base?

Bridge IDs:
– Lots – Grid view (Id: f1xno)
– Earlier error ref: 6lm5o/32046

Thanks!

2

Hey @wjpinvestmentsar :flexed_biceps:

Thanks for the detailed troubleshooting you’ve already done — recreating fields, duplicating bridges, and reconnecting tokens are exactly the right steps to try.

This “Setup incomplete” error with linked fields being ignored is definitely something we need to investigate more closely. Before we dig deeper with the team, let’s verify a few things:

Reference Field Sync Ordering

CMS Bridge requires a specific sync order for linked fields to work properly:

  • Children collections must sync first (the collections your linked records point to)
  • Parent collections sync after (the collections containing the linked record fields)

If your sync order was off, it could cause reference fields to appear incomplete. Could you verify you’re syncing in this order?

Current Field Mappings

In the CMS Bridge dashboard for the affected bridges (especially f1xno):

  • Are all the Airtable fields still present and visible in the mapping interface?
  • Do the field types still match what CMS Bridge expects (e.g., “Linked record - Single” vs “Linked record - Multi”)?
  • Is the connection icon showing green (successful link) or grey (unsuccessful)?

Fresh Configuration Pull

Sometimes disconnecting and reconnecting the integration entirely can help if the mapping got into an inconsistent state. Worth trying if you haven’t already.

What would help us diagnose this:

Could you share:

  • Screenshots of the CMS Bridge dashboard showing the “Setup incomplete” error
  • Screenshots of your Airtable base field configuration (especially the linked record fields)
  • Any recent changes you made to the Airtable schema before this started

Your error reference ID (6lm5o/32046) is really helpful — that lets our team look up the specific failure in the backend logs. I’m looping in @Support-Luis and @Support-Pedro on this. Your hypothesis about a cached schema issue is reasonable given the symptoms, and they’ll be able to investigate whether there’s a backend state that needs clearing for your specific base.

Let us know what you find with those verification steps :folded_hands: