Error Reference

Horizontal discovery pattern timeout: scan did not complete

Horizontal discovery pattern timeout: scan did not complete

Where this appears

This error appears in the Discovery Log (Discovery > Status) and in ECC Queue records when a horizontal discovery pattern fails to complete within the configured timeout period. It occurs during scheduled discovery operations or manual discovery scans when scanning IP ranges for devices and configuration items.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Horizontal discovery pattern timeout: scan did not complete" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

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)

Fix

Step 1: Navigate to MID Server > Status and check the MID Server health, CPU usage, and memory consumption to identify resource constraints.

Step 2: Review the Discovery Log at Discovery > Status to identify the specific IP range and pattern that timed out, noting the scan duration and scope.

Step 3: Check the discovery timeout settings by navigating to Discovery > Properties and reviewing properties like glide.discovery.timeout and glide.discovery.horizontal_timeout.

Step 4: Reduce the IP range scope by splitting large ranges into smaller subnets in the Discovery Schedule configuration to decrease per-scan workload.

Step 5: Increase MID Server resources by allocating more CPU cores, RAM, or adjusting the concurrent discovery thread count in the MID Server configuration.

Step 6: Test network connectivity from the MID Server to sample hosts in the target range using ping and port connectivity tests to identify network issues.

Step 7: Consider increasing the discovery timeout values if the current settings are insufficient for the network environment and scan complexity.

Step 8: Monitor subsequent discovery runs through the Discovery Status dashboard to verify that the timeout issues have been resolved.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue