Top-down Service Mapping discovery produces no ECC queue entries when no MID Server lists Service Mapping under Supported Applications<!-- /*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: ; } } IssueTop-down Service Mapping discovery is triggered for an entry point and nothing happens. Discovery Status stays at Starting Discovery, no ECC queue entries are created, and no error is shown.SymptomsDiscovery Status never progresses past Starting Discovery.Zero ECC queue entries for the run.No UI error and no MID Server log activity.MID Servers are Up and Validated, and horizontal Discovery works on them.MID Server Supported Applications contain entries such as Discovery, MID Server Management, Orchestration and Cloud Management, but no Service Mapping and no ALL.CauseMID Server selection for a top-down request requires a MID Server whose Supported Applications include Service Mapping or ALL. With no eligible MID Server, selection returns no candidate and the request terminates before any probe is written to the ECC queue. Zero ECC queue entries means the failure occurred before MID dispatch, not on the MID Server. This is a configuration gap rather than a product defect.ResolutionOpen MID Server > Servers and select the MID Server that should serve Service Mapping.Add Service Mapping to its Supported Applications, or set it to ALL.Verify Capabilities cover the protocols required by the entry points in scope, including cloud and REST based entry points.Verify the MID Server is Up and Validated and that its IP ranges include the targets, or that it serves All ranges.Confirm no default MID Server gap exists for the application and range combination.Rerun top-down discovery and confirm ECC queue entries are created and status progresses past Starting Discovery.Additional informationIf ECC entries remain absent after Service Mapping is added, rule out a prior cancelled run leaving a stale request state before pursuing a defect. Related: DEF0685805, DEF0058515, DEF0503924.