Incorrect Error: "Unique value is already in database"?

Hi there,

I’m having an issue syncing from Airtable to Webflow… when I try I get this error:

{“message”:“Validation Error”,“code”:“validation_error”,“externalReference”:null,“details”:[{“param”:“slug”,“description”:“Unique value is already in database: ‘locker-v1—landing-a’”}]}

However, I have deleted all the CMS items for this in Webflow… I thought that would solve this issue, but there is still a conflict?

How should I proceed??

1 Like

I tried deleting CMS-B: Webflow ID, CMS-B: Webflow Slug, and Sync Time, but that didn’t seem to change things…

Hi @rob2, even if you delete Webflow CMS items, the slug values still persist in Webflow’s backend, as in, they’re not fully deleted immediately and CMS Bridge picks up on that.

So, please sometime (a few hours) for Webflow to delete the slug values from it’s backend.

If you need to create those items immediately, then use new slug values and update them at a later point.

Thanks for the reply…

So I waited, and synced, and it worked… Everything synced…

However, a new issue started… The CMS items were then published by my employee in Webflow, and I tried to update them from Airtable once again…

Now it’s deleted all but 1, and gave this error… But there are no further details in CMS-B: Message.

Can you help me understand what is happening? Should I only be publishing CMS items from Airtable maybe? Since it’s already published…

Also, it keeps making NEW CMS items, … I have no idea why

here you can see 2 entries in Webflow with the same Airtable ID… both made from Airtable sync at different times…

Hi @rob2,

Now it’s deleted all but 1, and gave this error… But there are no further details in CMS-B: Message.

that 1 item isn’t deleted because it’s blocked by Webflow, as it’s referenced in a different CMS collection.


I don’t have the full picture as to why it’s deleting records, instead of updating them. So, can I request you to schedule a call with me (https://calendar.app.google/r49oB5wNn9M5Ya3r9) and we can resolve it in real-time?

Sure!

I made a call reservation for tomorrow morning… Thank you, looking forward to it

Hi @rob2, I had a nice call with you today.

To summarize, you’re using 1 Table, in which you have multiple Views; Each View has a corresponding Webflow CMS Collection and a CMS Bridge Connection.

So, you will need unique Mandatory Fields for every CMS Bridge Connection.

Please let me know if it’s working?

Thanks!

This is truly irritating! Even though you’ve deleted the CMS items in Webflow, the slug might still be cached or stored in the Webflow database. Try checking the Webflow Editor or Designer to see if any archived or draft items are holding onto the slug. If that doesn’t help, try renaming the slug slightly and syncing again. Also, clearing project backups and republishing might resolve any lingering conflicts. Let me know if that works!

1 Like