Transfer the missed customer updates from an update set to an instance where that update set has already been previously committedSummaryHow to move the missed customer updates of an update set to an instance where the update set is already committed previously in that instance Consider the below scenario : An update set has been retrieved from DEV to TESTIn DEV instance, for e.g there are 450 customer updates whereas in TEST instance there are 250 customer updates which means there are 200 customer updates missing in TEST instanceReleaseALLInstructionsNotice that in DEV instance, the update set might have been initially completed and later moved to in progress and made changes and hence these later changes are not retrieved to TEST. So before making the update set to Completed in DEV instance, there might be 250 customer updates. After making it to complete, user might have retrieved it in TEST and hence you find those 250 customer updates in TEST instance. After retrieving and committing that update set in TEST instance, the user might have changed the update set from Completed to In Progress in DEV instance and had extra 200 customer updates which in turn shows as total 450 customer updates. As you have already committed the update set in TEST instance with 250 updates, you wouldn't get the other 200 customer updates which is expected. As a best practice, once an update set is complete, do not change it back to In progress. Instead, create another update set for the rest of the changes, and make sure to commit them together in the order that they were created. Below are the steps to fix the issue in this scenario: To fix the issue, in DEV instance , navigate to the sys_update_xml table and filter the records with the update set (which is having issue) and identify the missing customer updates (200 updates)Create a new update set and from the above step, for the missing customer updates record, in the column update set, mention the new update set which was created and save the recordsCheck if the customer updates are captured in newly created update set or not.Complete the new update set and then retrieve it in TEST instance.Related LinksYou can refer to the documentation Get started with update sets and refer to the section Working with update sets for more details. Also, you can refer to the community article How to copy all the customer updates in a correct update set