Service Mapping - Scheduled discovery producing different result compared to UI Action Triggered Discovery from Service MapIssue There seems to be some corner cases where a Scheduled Discovery of a Service Map will produce a different result than that of the Discovery triggered within the Service Map by the "RUN DISCOVERY" UI Action.ReleaseAny and ALLCauseAs these are corner cases the exact cause cannot be determined, however there is a workaround.ResolutionChange the entry point to the FQDN of the host - using the IP Address as the entry point seems to be exploiting something during scheduled discoveries on this, however due to the nature of the different pieces involved it could be a configuration issue.