Clone Option "Preserve In Progress Global Update Sets" - NOT WORKING

G24
Kilo Sage

‎06-04-2023 12:41 PM

Hello Smart People,

 

It seems like this option is NOT WORKING for me when I clone from Production to Dev.  My Update Sets were not preserved on Dev and are not appearing in the table "sys_remote_update_set" on Dev after the Clone.  They also are not appearing in the "Local Update Sets" table (but that is expected).  Before the clone, I confirmed that they were all in the Application "Global" and also that they were all in a state of "In Progress".  And they were certainly created within the last 90 days; at least most of them were.

 

Our instances are on the following version: glide-utah-12-21-2022__patch1-hotfix1a-04-10-2023

 

My Clone Settings were as follows:

A.png

 

And the Clone Log was as follows:

B.png

 

What can I do to debug this problem, or figure out why our In Progress Global update sets were not preserved?  Thank you.

 

0 Helpfuls
  • 298 Views
1 REPLY 1

Bert_c1
Kilo Patron

‎06-04-2023 01:54 PM

Hi Geoffrey,

 

That may be a known problem, as with the "Preserve users and related tables" option that many times did not provide the expected experience. When I last worked in Support, neither worked as users expected.  You can search for related KBs and Known Problems.  If your clone was recent, you can "roll back" the clone.  Also, you may want to create a Support Case to get current status on those clone options.

0 Helpfuls