Backwards compatibility API

Hi,

We are using the API to move things between our environments. Today we have a ‘new’ version on our test environment and we cant push any change to our other environments because something changed in the identifiers.

Please keep this in mind when pushing new versions, now we have to wait until this new version is on our production environment.

This isn’t the first time this has happened, that’s why I made this post.

Hi @rolf

Thank you for letting us know, and we understand the frustration this is causing, especially since this isn’t the first time you’ve run into it.

This is most likely related to the version gap between the previous LTS release and the new version currently on your test environment. Over that period, a number of changes accumulate, including changes to identifiers, which is what’s preventing your changes from being pushed to your other environments right now. In your specific case, we’ve already followed up separately via a support ticket, and as agreed, we brought forward the update of your production environment so you could continue pushing your changes without waiting for the next scheduled release.

We’ve also shared this as feedback with our Product Development team, so it can be taken into account when planning future LTS versions.

Please let us know if there’s anything else we can help with.