Discovery status created with an empty scheduled job field and Discover field is set to subnetIssue <!-- 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; } --> Discovery status created with an empty scheduled job field and Discover field is set to subnet as in the below screenshot. CauseThese discovery status are created by scheduled job "Subnet Discovery". https://<instance-name>.service-now.com/nav_to.do?uri=sysauto_script.do?sys_id=b969b06bdb213340e1c3c3af299619d3 This scheduled job calls the script include "SubnetAcceleratorManager" which triggers the subnet discoveries. https://<instance-name>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=b28f1a37c3d20300e412bea192d3ae33 This below table has more information on the data collected in the discoveries. https://<instance-name>.service-now.com/automation_status_set_list.do ResolutionDisable the scheduled job if you do not want the jobs to run.