How does the Orlando clone option 'Preserve In Progress Update Sets' work?DetailsIn Orlando a new clone option has been provided that will preserve any update sets that are currently in a state of 'In progress' on the target instance. This new functionality is intended to help the customer when cloning over a development instance and prevent the need for manual preservation steps. By default the option is not selected when you schedule a clone but you can select the "Last 90 days" from the dropdown to trigger it. How does the new functionality work? When this functionality is active the following actions will be taken on the instance that has been used as the clone target. The 'in progress' update sets will be moved to the Retrieved Update Set (sys_remote_update_set) table after the clone.The admin user will then be expected to preview this update set and commit it.This will then re-apply the updates and also move the update set back to the sys_update_set tableThe update set can then be changed back to a state of 'In progress' and development can continue. Please note that currently this will only work with Global update sets. Additional InformationDo not keep too many large in-progress update sets or else it could lead to clone failure. The run-node script has a timeout value of 4200 seconds or 70 minutes and will fail if there are too many updates to preserve. One example of a clone failure was from an instance preserving more than >700,000 updates.