Opening/Downloading an ACC Plugin (asset) record "touches" it, preventing it from being updated during next store app upgradeDescriptionOpening an ACC Plugin (asset) record in a form "touches" it, preventing it from being updated during next store app upgrade. This may be done to download a taar.gz attachment to inspect the contents, or to check if it had been customised in the first place, but end up causing it to be treated as a customisation, with sys_update_xml and sys_update_version records being created. When the Instance app is next upgraded, the record will be Skipped, and be replaced with the new version from the app. That is expected behaviour once a record is touched. The symptoms seen could be nearly anything, but likely to be seen in check results, due to mis-matched code at check runtime, such as missing function/method errors. Ruby scripts from one plugin often call scripts from other plugins, so all apps generally need to be upgraded at the same time, and their plugin assets can't be skipped.Steps to Reproduce Maybe just open the record, or maybe you have to click download (it's unclear)Observe that the file was updated in the sys_update_version table (I think it will show up there. Or you can try to perform an upgrade and look at the upgrade log)Workaround<p>This problem has been fixed in ACC-F 2.10.1. If you are able to upgrade, review the <strong>Fixed In</strong> or <strong>Intended Fix Version</strong> fields to determine whether any versions have a planned or permanent fix.</p> To revert to the out-of-box version, to upgrade individual plugin assets, after an app upgrade, see:KB1157033 How to revert ACC Plugins (assets) to out-of-box versions to solve Skipped upgrade related code mismatch issuesRelated Problem: PRB1554342