Repo pushes all Custom App objects in sys_update_version are in a 'History' stateIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Steps to reproduce:- Make a change to any catalog item (change the 'owner', update a variable, ... just something to check when it promotes to target instance)- Attempt to deploy the 'Enterprise Collaboration Services' application to the Test environment- Once the deployment is complete, look at the version history in sys_update_version. Notice it ALL seems to be in 'History'.• Go into the objects you attempted to change. Notice they did not change in target instance.• Go into the sys_store_app record for that application in target instance.• Notice, the version DID increment, even though none of the changes actually posted. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Even after trying: • converting the app scope - to 'Development Mode' in the application record, then setting it back to 'Application Repository' mode, and then going into 'My Companies Applications', and setting/downloading/installing the most recent version from the repository. • updated all of the records for that app scope in sys_update_xml to have the 'Replace on upgrade' value set to 'true'.• after reverting the most recently updated sys_update_version record, for one of the catalog items, to current. Unfortunately that can Delete the catalog item. none of that has worked. Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Best practices: • ensure Source Control is Linked: Confirm your development instance is linked to your source control repository and that the catalog item belongs to an application managed by source control.• Before making changes, create a new branch from your application's main branch in ServiceNow to isolate your modifications.• Edit the Catalog Item in Service Catalog > Catalog Definitions > Maintain Items > [pick one] > [make changes]• If using the Catalog Builder, you may need to "check out" the item for editing in that interface, make changes, and then "submit" the modified item to save the draft.• > save > commit to source >• Application Navigator > System Applications > My Company Applications or Source Control (depending on your setup).• > Use the "Commit Changes" option to push your modifications from the local instance to your remote repository branch. This will capture all the changes you've made to the catalog item and its related records (variables, etc.).• Verify in sys_update_xml that there is no other update set pushing alongside [conflicting with] the repo push. The update set column there should be null.This process ensures that all changes are versioned and can be tracked, merged, or deployed to other instances (like Test and Production) via the source control integration, which is the standard practice for applications under source control rather than using traditional update sets. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Zurich 4 Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Check when you deploy your app that there is no sys_update_xml records for the catalog item. If you see a CB_ update set automatically getting created, this is because updates to Catalog Items made through Catalog Builder are no longer being tracked in manually created and active update sets, and instead, the system will create CB_ update sets. This is an OOB behavior and cannot be changed.If you want to know how to disable tracking through Catalog Builder, or how all of your updates are to be captured by the currently selected update set, instead of spreading them out across multiple update sets and then having to move the updates to your update set.... Unfortunately, if one is using a catalog builder, then the updates are captured automatically. That is the expected behavior and cannot be disabled or changed to capture it via normal update sets. Guideline:• The upgrade engine will see you made changes to a file,• then checks to see if there are any customizations in the form of sys_update_xml records.• If there is a customization, it creates a skipped record 'to review' in upgrade history.• If it doesn't see a customization in sys_update_xml, it goes ahead and updates the file. If an app with tons of sys_update_xml records, in the all target instances, were installed via update set. The fix is to change the 'replace on upgrade' flag to true on all of them.When you do this, in the History, the sys_update_version will look strange, because it will say the default update set is the latest version, but it will give you the update to these flagged files okay.It is okay if you don't care about an app, to try deleting the sys_update_xml records to see if the history says it came from the store instead of an update set. pre-clone backups recommendation depending on if it's installed on dev:• back up update sets in dev by exporting the application as XML, then import it after the clone.• however retrieving that update set on the test instance and commiting it would then have an issue, because it would bring all your sys_update_xml records. But limited to dev is okay.• when cloning, it is typically not backed up, it's just redeployed in test instance after.• To copy a working app down from production, switch the app from repo mode to development mode; then you can publish a new version. Then put it back to repo mode, then reinstall it back to prod to match the version number now in the repo.