Discover Now displays "Can't discover CI because this IP Address is not found in any Discovery Schedules"<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000; max-width: 100%; } .kb-wrapper h2 { font-family: Lato, sans-serif; font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 6px; margin-top: 28px; margin-bottom: 12px; } .kb-wrapper p, .kb-wrapper li { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; } .kb-wrapper ul { padding-left: 24px; margin: 8px 0; } .kb-wrapper ul li { margin-bottom: 6px; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; font-size: 11pt; } .kb-wrapper .kb-steps { list-style: none; counter-reset: kb-step; padding-left: 0; } .kb-wrapper .kb-steps > li { counter-increment: kb-step; position: relative; padding-left: 40px; margin-bottom: 10px; } .kb-wrapper .kb-steps > li::before { content: counter(kb-step); position: absolute; left: 0; top: 2px; width: 26px; height: 26px; background: #032D42; color: #63DF4E; border-radius: 50%; text-align: center; line-height: 26px; font-weight: 700; font-size: 11pt; } .kb-wrapper .callout-note { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 12px 16px; margin: 16px 0; border-radius: 0 4px 4px 0; } .kb-wrapper .callout-note strong { color: #032D42; } .kb-wrapper .kb-screenshot { margin: 16px 0; text-align: center; } .kb-wrapper .kb-screenshot img { max-width: 100%; border: 1px solid #b8cfd8; border-radius: 4px; } .kb-wrapper .kb-screenshot .kb-caption { font-size: 10pt; color: #555; font-style: italic; margin-top: 6px; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper .kb-related-links { padding-left: 24px; } .kb-wrapper .kb-related-links li { margin-bottom: 4px; } Issue When you click Discover Now on a Configuration Item (CI) record, discovery does not start. Instead, an informational banner appears indicating that the IP address is not part of any discovery schedule. Symptoms The following info message appears at the top of the CI record when clicking Discover Now: Can't discover CI because this IP Address is not found in any Discovery Schedules Info message displayed on a CI record after clicking Discover Now No new discovery status record is created for the CI.The CI's IP address has never been included in a discovery schedule.Discovery works correctly for other CIs whose IP addresses are part of an active discovery schedule. Facts This applies to all currently supported releases.The CI must have an IP address populated.The IP address in question has no entry in the discovery_device_history table tied to a discovery schedule.A Quick Discovery of the same IP address does not create the required discovery device history record that Discover Now depends on.This is out-of-the-box (OOB) platform behavior, not a defect. Release All currently supported releases. Cause This behavior is by design. When you click Discover Now on a CI, the platform looks up the discovery_device_history record for that CI's IP address to determine how to discover the device — including which credentials, MID Server, and classification rules to use. That history record is only created when the IP address has been discovered through a discovery schedule. A Quick Discovery of the IP does not generate this record. Because no discovery_device_history entry exists for an IP that has never been part of a discovery schedule, Discover Now cannot execute and displays the informational banner instead. Resolution To use Discover Now on a CI, the CI's IP address must first be discovered through a discovery schedule. Complete the following steps: Navigate to Discovery > Discovery Schedules.Open an existing discovery schedule that covers the relevant network range, or create a new one.Confirm that the IP address of the CI is included in the schedule's IP address range or list.Run the discovery schedule. This creates the required discovery_device_history record for that IP address.After the scheduled discovery completes successfully, navigate back to the CI record.Click Discover Now. The option now functions as expected because the platform can reference the discovery device history for that IP. Related Links Discovery schedules — ServiceNow product documentation (latest)Quick Discovery — ServiceNow product documentation (latest)Discover Now — ServiceNow product documentation (latest)