What happnes to the previewd not commited update sets in prod after clone?

[saint]

I have around 30 update sets, which are previewed and not commited in production. I don't need the updates from these, what should i do them in production before cloning? 

I read somewhere that these will get cloned too and will stay previewd in test and dev, which doesn't make sense.

[Brad Bowman · Accepted solution]

A clone copies what's in production to other instances, so yes, the update sets will appear in the cloned-over instances in the previewed state.  You can exclude them from the clone, or just delete them in production like any other unneeded data.

[GlideFather]

Hi @saint,

either delete these previews or exclude them from the cloning (preservers x excluders)..

[kaushal_snow]

Hi @saint ,

Previewed update sets in Production are cloned too, they appear in the target instance still marked as Previewed (not committed), which often leads to confusion.

If an update set was already completed in Production, it may still get retrieved in the clone environment, often appearing again as Previewed, causing duplication headaches.

*** You can follow to Avoid Post Clone Confusion ***

1. Before cloning, set any completed update sets in to Ignore. This prevents them from reappearing as retrieved or previewed in the target instance.

2. Delete unwanted previewed and loaded retrieved update sets in Production (and optionally in Pre Prod or Dev). This ensures they’re not cloned over.

3. Configure your clone to exclude tables like sys_update_set and sys_remote_update_set. This avoids copying update set related data entirely.

4. Backup Using XML if You Need to Preserve

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.