MID Server not a member of this clusterIssue When running a discovery schedule that has a MID Server Cluster selected - you may see the error: MID Server not a member of this cluster: MID Server with name MIDSERVER_NAME is not in cluster CLUSTER_NAME. You will notice that the MID Server mentioned isn't a part of the cluster than it mentions.CauseWhen discovery starts, it will initialise the discovery schedule, the discovery ranges and a default MID Server. The default MID Server will come from the Discovery Schedule being run if its is configured correctly - however, if it is not configured to use a specific MID Server, then the first functional MID Server that is returned from the Database will be picked as default and used, this so happens to be the MID Server you're seeing in the error message. When we launch the Shazzam probe, it will notice that 'Shazzam Cluster Support' checkbox is not is not checked on the Discovery Schedule, Discovery logic unfortunately does not pick the MID Servers from the Cluster specified, and instead, will use the default MID Server. Now, because we have a Cluster configured in the Schedule, the discovery logic will check to see if that MID Server is a part of that cluster, and if it is not, the error message will be logged and the Discovery will be cancelledResolutionFor ALL schedules configured to run with MID Server Cluster, check the box 'Shazzam Cluster Support'. It is checked by default when creating schedules from UI. It may be that there are many schedules created programmatically, thus 'Shazzam Cluster Support' wasn't set to true and this error was present.