Update set Logs not available for update sets from "Show commit log" | Batch update setsIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms An update set is committed and there are no update set logs available Release Starting Jakarta and later Cause This is a child update set and check the parent update set for the commit logs. Resolution In order to find the parent of the current child update set, go to local update set > open the child update set and look for "parent" field. Additional Information 1. if update sets are batched together, only the parent update set will have the Update set logs listed. And only after the entire batch of update sets are committed the logs to show up under "Update set logs" 2. Graphical representation of parent and child update sets can be viewed by navigating to the source or target instance> Local update set > choose the batched update set record > Click "Visualize Update set Batch" related link in the bottom