--- sourceDocument: Brazil ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Managing upgrade risk # Managing upgrade risk {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Managing upgrade risk This feature helps ServiceNow customers manage potential conflicts during upgrades caused by customized and skipped metadata files. Upgrades can be complicated when ServiceNow updates files that have been customized, leading to conflicts especially in skipped metadata files. The system now notifies you with UI messages on form pages about these risks, helping you proactively address them. Show full answer Show less ## Key Features * **UI Notifications:** You receive contextual UI messages on metadata file forms indicating risk levels based on customization and potential future updates. * **Risk Categories:** Files are classified as high risk, medium risk, or non-risk based on the likelihood of changes in future releases and whether they are customized. * **Guidance on Modifications:** * Avoid editing high and medium risk skipped metadata files unless absolutely necessary. * If high or medium risk files are customized, it is recommended to revert them to the Base System to prevent upgrade conflicts. * Non-risky files (customized or not) do not show warnings and can be modified with less concern. * **High Risk Customizations Menu:** Provides a consolidated view of your customizations overlapping with ServiceNow's high and medium risk files, using a virtual table refreshed regularly. * **Risk Data Storage:** High and medium risk files are tracked in the sysmetadatavolatility table, which is updated automatically during family upgrades. Modifications to this table are discouraged. ## Practical Implications for ServiceNow Customers This capability enables you to better anticipate and mitigate upgrade conflicts by identifying risky customizations early. The UI messages and the High Risk Customizations menu support informed decision-making about whether to modify or revert metadata files, reducing the chance of costly upgrade issues. Following the recommendations helps maintain system stability and simplifies your upgrade process. You will be notified of the possible conflicts that might result due to several customizations in a skipped metadata file, with a new UI message on the form pages of the metadata files. One of the major conflict areas during an upgrade is resolving conflicts for skipped metadata files that are released by ServiceNow® but have been customized. These conflicts result from multiple users updating the same files. ServiceNow might update the code in the files which you have customized over time. Whenever you install an application or a plugin, you often customize them as per your requirements. During the next upgrade, you might have several skipped records depending on the previous customizations. Important: Avoid modifying the high risk and medium risk (if possible) skipped metadata files that can potentially cause conflicted skipped metadata files in your next upgrade. You can edit the files if the modifications are absolutely required. The purpose of the UI message is to inform you about potential complications that might arise during the upgrade process, especially if any high-priority files have been modified. The notification is of the form of UI messages on the form pages of the metadata files. The UI message varies based on the severity of the files. * Medium risk and non-customized: The medium risk files that are not customized might be updated in future releases. It is recommended not to modify these files unless necessary. * High risk and non-customized: The high risk files that are non-customized might be updated in future releases. It is recommended not to modify these files unless necessary. Note: You can proceed to modify these files if the changes are absolutely required. The following modal shows up. * High risk and customized: The high risk files that are customized might be updated in future releases. It is recommended to revert them to the Base System to avoid conflicts. * Medium risk and customized: The medium risk files that are customized might be updated in future releases. It is recommended to revert it to the Base System to avoid conflicts. * Non-risky and non-customized: You don't see any warning for this condition. * Non-risky and customized: You don't see any warning for this condition. {#uc-manage-upgrade-risk__ul_nn3_wvr_1bc} ## High Risk Customizations menu {#uc-manage-upgrade-risk__section_syh_mjb_2cc} The High Risk Customizations menu item presents the overlap between ServiceNow's high and medium risk files and your customizations. They are stored in a virtual table called v_metadata_customization_risk, and is refreshed after a set period of time or when you select the Refresh on the list view. ## Risk files storage {#uc-manage-upgrade-risk__section_xrd_fkb_2cc} The high risk and medium risk files are stored in the new sys_metadata_volatility table. Note: It is recommended not to modify the sys_metadata_volatility table and is automatically updated for every family upgrade. The sys_metadata_volatility table is not a part of the menu item in the navbar. Note: Risk is determined by the likelihood of a given metadata file being modified, which is predicted based on trends in updates from recent releases. Some files that may not currently exist in the system will be present in the table to account for future installation of apps/plugins. **Related tasks** * [Create a skipped record rule](https://www.servicenow.com/docs/zNKW1E4~3r0pfB2p9X0kKw "Create skipped record rules based on your set conditions to define your customizations after an upgrade.") * [Execute a skipped record rule](https://www.servicenow.com/docs/Qhr2TMA21WiyCX~KgIWSgg#uc-execute-skipped-record-rule "Run skipped record rules based on your set conditions to resolve skipped records in an upgrade. The rules either execute automatically during an upgrade or can run on demand after an upgrade.")