The changes from "resolve conflicts" button are not reflected on target instance when moved via update set.Issue The changes from the "Resolve Conflicts" button are not reflected on the target instance when moved via update set. Post upgrade, skipped logs need to be checked. When the skipped logs are reviewed, resolved and captured in the update set in one of the environments, applying the same update set to the target instance will not Skipped Logs Status are not changing from Skipped Changes to Review to Skipped Changes Reviewed.CauseThe "update_synch" attribute is not set up on "sys_upgrade_history_log" table by default, so changes to this table will not be captured in update setResolution This is the expected behavior as the data changes to "sys_upgrade_history_log" table are not captured in update sets because there is no "update_synch" attribute for this table. Please note we suggest to not add the update_synch attribute to a dictionary record. When improperly used, this attribute can cause major performance issues or cause the instance to become unavailable. Adding this attribute is not supported. Please find the below documentation on "update_synch" attribute for your reference. https://docs.servicenow.com/csh?topicname=customizations-tracked-update-sets.html&version=latest