We have a script that applies the content model to a target space as part of our automated build pipeline. The script loops through all the content types and applies them one by one (each content type is stored as a separate file in git). We’re getting a new error on certain content types: 409 Conflict, which is a apparently a version mismatch.
To debug this, I exported our production space into a brand new empty space and tried to update the content model. I even got 409 Conflict errors on this import which is weird because I imported into an empty space. I shouldn’t get version mismatch importing into an empty space.
I looked it up on Contentful’s error page and it says this for 409: “This error occurs when you’re trying to update an existing asset, entry or content type, and you didn’t specify the current version of the object or specified an outdated version.”
Applying the content model works when I apply it to our TEST environment. I get these 409s when I apply it to our PRE environment. I compared the content types in the error message and I can’t see a difference.
Any thoughts on how I can debug this further?