How to repair a plugin using App Manager to resolve unexpected feature behaviorIssue <!-- /*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: ; } } Resolve unexpected or incorrect behavior in a ServiceNow feature where the underlying plugin may have missing dependencies, an incomplete installation, or a configuration issue. After installing or upgrading a plugin, the feature it supports may not behave as expected. One or more of the following symptoms may be observed: A feature that was previously working stops functioning after a plugin installation or upgrade.A plugin-dependent feature returns errors, produces no results, or behaves inconsistently.A plugin appears to be installed but one or more dependencies are missing or inactive.A feature works for some users or in some contexts but not others, suggesting a partial installation. 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: ; } } All supported releases Cause<!-- /*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: ; } } When a plugin is installed or upgraded, one or more of the following conditions may cause the feature to not behave as expected: A dependent plugin or store application was not installed or was not updated to a compatible version.The plugin installation did not complete successfully, leaving the plugin in a partially installed state.A required system configuration, business rule, or script included in the plugin was not applied correctly during installation.A prior customization or update set conflict prevented the plugin from setting up correctly. Using the Repair function in App Manager re-runs the plugin installation process without removing existing data, which can resolve missing dependencies and incomplete setup issues. 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: ; } } Use the Repair function in App Manager to repair the affected plugin. This re-runs the installation process and restores any missing dependencies or configuration. Warning: The Repair function re-runs the plugin installation. Review the impact of re-running the installation on any customizations applied to the plugin before proceeding. Contact ServiceNow Technical Support if you are unsure whether repairing the plugin is safe for your instance. Step 1: Identify the affected plugin Identify the plugin that supports the feature with unexpected behavior. If the feature depends on multiple plugins, identify all affected plugins. See [How to identify and verify Store application dependencies and their versions] for guidance on finding plugin dependencies. Step 2: Repair the plugin Go to All > System Applications > App Manager.Search for the affected plugin by name or plugin ID.Select the plugin to open its record.Select the additional actions menu (⋮) or the plugin options.Select Repair.Wait for the repair process to complete. Note: The repair process may take several minutes depending on the size of the plugin and the number of dependencies. Do not navigate away from the page until the process completes. Step 3: Verify dependent plugins After repairing the primary plugin, verify that all dependent plugins are installed and running the correct versions. Go to All > System Applications > App Manager.Select Sync Now to sync the latest available versions from the App Repository.For each dependent plugin, verify that the installed version matches the required version for the primary plugin.If a dependent plugin requires an update, select Proceed to Update and complete the update. For guidance on identifying required dependency versions, see [How to identify and verify Store application dependencies and their versions]. Step 4: Verify the fix After the repair and any dependency updates are complete, repeat the steps that originally reproduced the issue.Verify that the feature now behaves as expected.If the issue persists after repairing the plugin and updating all dependencies, contact ServiceNow Technical Support by submitting a support case. Note: If the feature is being verified in a non-production environment, confirm the fix in that environment before applying the same repair to the production instance. General guidelines for resolving plugin setup issues Follow these general guidelines when a plugin-dependent feature is not working as expected: Before repairing a plugin, check the system logs for error messages that identify which plugin or dependency is causing the issue. Go to All > System Logs > All and filter by the relevant time range.Verify that all plugins the feature depends on are installed and running compatible versions before attempting a repair.If a recent upgrade or update set was applied before the issue appeared, review the upgrade history or update set log for conflicts that may have affected the plugin setup.After repairing a plugin in a non-production instance, document the steps taken and verify the fix before applying the same repair to production.