MID Server is under-resourced with insufficient CPU, memory, or concurrent thread capacity to handle the discovery workload within the timeout period. (high likelihood)
The IP range being scanned is too large, containing too many addresses for the MID Server to process within the configured discovery timeout. (high likelihood)
Network latency or slow-responding hosts in the target IP range are causing individual probe operations to take longer than expected. (medium likelihood)
Discovery timeout properties are set too low for the scope and complexity of the discovery operation being performed. (medium likelihood)
Network connectivity issues or firewall restrictions are causing connection delays or packet drops during the discovery scan. (low likelihood)