Installed Scoped Applications from a Repository does not appear in Scope drop down under 'Scripts - Background' Module.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Question: Why the Scoped Applications installed from Repository that are developed on a different instance will not appear in Scope dropdown under Scripts - Background Module? Answer: "With regards to the question about the background script running on a scoped app installed through repository" - This functionality is not available in the base system. By default the scope options for background scripts only shows apps that were developed in the instance. This is the Out of Box behavior of the system. You are able to run background scripts only in global scope and scopes of applications that are developed on same instance. You can not select the scope of an application that has been installed on the instance. Example If we consider there are 2 instances, DevelopmentTest And below are the list of scoped applications developed on "Development instance" and installed on "Test Instance". x_ingg2_esmx_ingg2_investigatx_ingg2_time_writix_pl4_ice4u In this case, refer below how does the scope drop down will display under Scripts-Background Module on "Development instance and Test instance". select name, source, sys_class_name from sys_package where source like 'x_%' order by sys_class_name, source" From Development: select name, source, sys_class_name from sys_package where source like 'x_%' order by sys_class_name, source" From Test: There will be difference in "sys_class_name" for scoped applications on developed instance and installed instance for below applications. x_ingg2_esmx_ingg2_investigatx_ingg2_time_writix_pl4_ice4u Additional Information: A possible way to run a script in that scope is using a fix script. Please refer below documentation for fix scripts: https://docs.servicenow.com/csh?topicname=c_FixScripts.html&version=latest Please refer below community link to understand the difference between fix scripts and background scripts: https://community.servicenow.com/community?id=community_question&sys_id=3e427075dbeb5344200f0b55ca961945 https://community.servicenow.com/thread/288432