How the All Applications discovery schedule works

The All Applications discovery schedule in ServiceNow only triggers discovery on operational application service maps, not all existing maps. This article explains how this process works and why this limitation exists. 

When you select Discover Now from the All Applications discovery schedule, the system does not trigger discovery on all existing application service maps. Instead, it only processes maps that are currently in an operational state. 

Any supported release

The All Applications rediscovery follows these steps:

1. The system searches through all configuration items (CIs) that have the cmdb_ci_appl class and their related items. It only includes CIs that belong to Business Services marked as Operational.

2. For each identified CI, the system retrieves the incoming endpoint information.

3. The system locates the corresponding entry in the sa_endpoint_status table, which stores references to all endpoints.

4. The system changes the state value to waiting for discovery (value: 0) in the endpoint status table.

5. A scheduler sends the discovery request to the ECC Queue, which initiates the rediscovery process.

6. During rediscovery, if the system finds new outgoing connections, it adds them to the application service map.

Important considerations

• Only operational Business Services are included in the discovery process
• Non-operational maps are excluded from automatic discovery
• New connections discovered during the process are automatically added to existing maps