What happens when there are no available MID Servers in the auto-select process?

When there are no available MID Servers in the auto-select process, the system resorts to using the default MID Server designated for the Discovery application. The default MID Server is defined as part of the system's configuration and serves as a fallback option to ensure that discovery processes can continue even when other MID Servers are unavailable. This mechanism is crucial for maintaining continuity in discovery operations, particularly in environments where multiple MID Servers may be configured for redundancy or load balancing.

In scenarios where no MID Servers are available, using the default MID Server allows for the possibility of completing discovery tasks without interruption, ensuring the system remains functional and responsive. This capability to fall back on a default MID Server enhances the reliability of the ServiceNow Discovery process, minimizing potential disruptions in operations due to MID Server unavailability.