Catalo builder auto generated update sets (duplicate variables)

[CecileC]

Hi, 

I started recently to using catalog builder and I'm not sure to understand how the auto generated update sets are working:

In my dev instance, I worked on a new catalog for several days, making some changes according to the client's requests. Once it was done, I noticed  several US created in the process. I pushed them in Test instance (in the same order they were created) and there were a lot of errors to go through before being able to commit the update set. Most of the time it said that a newer update set had been found and when comparing with the local US, there was no difference..

At the end, I noticed that the variables, UI policies, UI actions, fulfillment steps... were  doubled or tripled...

Can someone explain what I am supposed to do with those US? How come it doesn't update the catalog like a normal update set? 

Thank you in advance !

[JR42]

Hi Cecile, hopefully you figured this out.  These CB update sets are a huge pain.

Ever since they started (sometime this year), I avoid using the Catalog Builder at all costs.

However, if I end up with a CB update set, I usually go into it and move all the updates to the update set I want them to be in.  Then I set the CB update set to Ignore.

[Sergio Bernal]

I have the same issue, Hope someone can help us.