Scope not found: application scope does not exist

A scoped application was uninstalled or deleted from the instance, but scripts still contain references to objects within that application's namespace. (high likelihood)

An update set was imported from a different environment where additional scoped applications exist, creating references to scopes not present on the target instance. (high likelihood)

A scoped application failed to install completely, leaving the scope in an inconsistent state while other code references it. (medium likelihood)

The application scope name was changed or the application was moved to a different scope, breaking existing cross-scope references. (medium likelihood)

Custom scripts contain hardcoded scope references with typos or incorrect namespace identifiers that do not match any installed application. (low likelihood)

Step 1: Navigate to System Applications > Applications to verify which scoped applications are currently installed and note their exact scope names.

Step 2: Check the Application Log at System Diagnostics > Logs > Application Logs to identify the exact script and line number causing the scope reference error.

Step 3: Use the Global Search or navigate to System Definition > Scripts - Background to search for all script references containing the missing scope namespace.

Step 4: If the referenced application should exist, reinstall it from the ServiceNow Store or import the required update set containing the application definition.

Step 5: If the application is no longer needed, update all script references to either remove the cross-scope calls or replace them with equivalent functionality from available scopes.

Step 6: For Business Rules and Script Includes, check the Condition field and Script field for hardcoded scope references and update them to use valid scope names.

Step 7: Test the corrected scripts in a sub-production environment before deploying to production to ensure all scope references resolve correctly.

Step 8: Clear the cache by navigating to System Diagnostics > Cache Stats and clicking Flush All to ensure updated scope references are properly loaded.