Discovery APIProxyProbe stuck in ready state for specific MID ServersIssue Discovery schedules stuck in active state / cancelled due to APIProxyProbe in ready state.The ecc_queue records gets processed on some MID Servers.And do stuck in Ready State for other MID Servers.ReleaseAllCauseThis in most cases is due to the domain the MID Servers are defined.For a domain separated instance, if a MID Server is in global domain, it will be considered in discovery schedule for any Domain.Thus if the MID Server host machine is from a different domain but configured as global will attempt to process these ecc queue records.And get stuck in Ready State.ResolutionDefine MID Servers in appropriate domains.Schedule discoveries with same domain.Discovery will process all the records and complete successfully.Related LinksUseful docs: Domain Separation and DiscoveryMID Server domain separation