Cloud discovery schedule created to run with a mid-cluster is picking a different mid server other that of the mid-cluster when all the mids in the cluster are down or paused - Known Error

Cloud discovery schedule created to run with a mid-cluster is picking a different mid server other that of the mid-cluster when all the mids in the cluster are down or paused Description Cloud discovery schedule created to run with a mid-cluster is picking a different mid server other that of the mid-cluster when all the mids in the cluster are down or paused Ideally the schedule should get cancelled in this case.

Steps to Reproduce

> Create a cloud discovery schedule and set mid selection method as "Specific MID Cluster"

> Pause or Stop the MID servers in above cluster, and make sure there are other MID servers running on the instance with cloud discovery required applications / capabilities

> Run the schedule. It should be canceled as there's no MID server available in the specified cluster.

However the schedule starts on other MID servers.

Workaround There is no known workaround for this issue. If you are able to upgrade, review the "Intended Fix Version" section below below to determine the versions that have a permanent fix.