Clone / Upgrade / Update sets

Kenny_vl
Tera Contributor

I need some help in understanding what has happened here but let me first give you the scenario.

 

On the 13th of March, we cloned production to a sub-production target. Before this clone action, I removed all remote update sets with a state of “Previewed” from production and retrieved the update sets.

Sub-production was then upgraded on the 14th of March.

 

When I retrieve update sets on production today, I noticed that certain update sets (which were already committed before the clone) appear again with a state of “Previewed”.

At this point, it is only about ~10 update sets and I can do the verification manually but in the future this number will most likely be higher. This is why I am trying to understand the process here so that I can prevent this from happening again in the future.

 

Maybe it’s because it is Monday morning, but I can’t manage to wrap my head around this to understand completely and I would like to count on the community to help me out here. 🙏🏻

5 REPLIES 5

AlainT1
Tera Guru

Hi Kenny,

I have the exact same issue in our instances.  I read the answers here but couldn't find one that made sense or that would prevent the duplicates from happenning.  Have you found a solution that works for you?

Thank you

Alain