How to revert ACC Plugins (assets) to out-of-box versions to solve Skipped upgrade related code mismatch issuesSummary<!-- /*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: ; } } Agent Client Collector (ACC) "plugins" are tar.gz files that contain the Ruby scripts that execute when Checks are run. Others ACC plugins act as libraries that get called from those scripts, and so those inter-dependencies make it very important that no plugin upgrades are skipped when ACC Apps are upgraded in the instance. Mismatched versions for ACC Plugins often cause file/script not found, or function/method not found errors in the acc.log file or ecc_queue input response. Before looking at folder permissions, or the cache system, you should confirm all plugin records/attachments are the current out-of-box version. There has been a known problem, not fixed until ACC-F 2.10.1, that made it very easy to accidentally cause these plugin records to get updated (even by ServiceNow tech support!), sometimes while apparently just looking, and so an attachment that is synched to the MID Servers and ACC cache remains on the old often incompatible version. See: PRB1554342 / KB1158004 Opening/Downloading an ACC Plugin (asset) record "touches" it, preventing it from being updated during next store app upgrade Note: Importing records from another instance as XML, or replacing attachments on these records, is not a solution, as the record remains custom and will still be skipped in future upgrades.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: ; } } Any Instructions<!-- /*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: ; } } Do this process for each Version record in each Application. Open a list of the sys_update_version table, and filter on:Type = Agent Client Collector Pluginand, State = Current Switch your session to the Scope of the application. e.g. "Agent Client Collector for Visibility" for this example. Open one of the version records. The following would need doing for each of these records. The Versions related list will show that the "current" version is not the most recent Store Application version. Tick the checkboxes of the Current custom version, and the most recent Store Application version, and from the list actions select Compare. On the Compare diff form you can see what fields are different. Note: There may not actually be any differences, but the system still considers the current version a custom version that should be skipped in the next upgrade. Click Revert to Selected Version. You will be returned to the version record, and the Versions related list should now show the Current version is the most recently recorded out-of-box Store Application version. Go back to the list of all versions. Open any other records that still need doing and revert them in the same way. Once you have done all the version records that did not should Source as the Application, you can switch your session to another scope and revert the plugins from that scope. e.g. Agent Client Collector FrameworkRelated Links<!-- /*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: ; } } You might see the Current version source value is already a Store Application, and would assume you have the latest OOTB version, but it's not the most recent Store Application version. You still need to revert to the most recent "recorded at" Store Application version listed to be sure you have the most recent plugin attachment.