How to find and revert skipped SAMP plugin files to base systemIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After you activate SAMP or its related plugins, you may receive an email about reverting customizations. You need to find the skipped files in your instance to validate and revert them to base system. This article shows you how to find and revert skipped files related to SAMP plugins and their dependent plugins. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Madrid and later Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Revert Customizations module is located in the Software Asset application under Administration. To access it, go to All > Software Asse > Administration > Revert Customizations. This page provides a list of all customization files that you can review and revert. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Method 1: Use the Revert to Base System action Go to All > Software Asset > Administration > Revert Customizations.Select the files you want to revert or select all skipped files.Select the Actions menu at the bottom of the page.Select Revert to Base System. Method 2: Manually revert files when base files are missing If you do not see the Revert to Base System action (for example, after cloning an instance), follow these steps: Go to All > System Update Sets > Retrieved Update Sets or navigate to the sys_update_version table list view.Search for the file you want to revert.Open the latest version of the file by sorting the Recorded at column from Z to A.Compare the file contents with the source code.If the contents match, revert to this file.Mark the file as reverted in Upgrade history. Method 3: Contact ServiceNow support Contact ServiceNow technical support to run revert scripts that revert all related files to base system. ServiceNow requires your approval before running scripts in Scripts - Background. Validate reverted files After you revert files, validate that the reversion was successful: Note the number of files before you revert the skipped files.Copy the following URL and replace INSTANCE_NAME with your instance name: `https://INSTANCE_NAME.service-now.com/sys_upgrade_history_log_list.do?sysparm_query=sys_updated_onONLast%2030%20minutes@javascript:gs.beginningOfLast30Minutes()@javascript:gs.endOfLast30Minutes()%5Esys_updated_by%3Djavascript:gs.getUserID()%3B&sysparm_view=`Open the URL and verify that the count matches the number you noted earlier.