Number of Targeted IPs in Discovery Home is changing between runs of a discovery scheduleIssue The number of Targeted IPs is changing each time the schedule is run, yet we are not changing the IP Range Set or IP Ranges that the schedule is using.This variation in Targeted IPs can be seen from Discovery Home > Schedules when viewing the last 10 runs for the discovery schedule. CauseMid server was down when discovery run. Checked ecc queue for Shazzam error "Shazzam fail over for MID Server Selection Method Auto Select is currently not supported. Abandoning this Shazzam and continuing the rest of discovery." we assign a portion of ips to any proper mid server at the beginning of the discovery. If you look at the output record for shazzam you can see the following parameters :full range : shows the whole ip ranges to discover for that schedulemid_range: shows the range of ip addresses which is assigned to this MID Serverrange: shows the set of ips that in the current patch will be scanned Every time MID Server comes back with its input for one batch, the second batch from mid_range will assign to the mid server. Since MID server was identified as down and we don't have input record back from the MID Server the rest of ips that was supposed to be assigned to that MID Server will be missed.ResolutionMid server down during discovery is causing the issue. Check mid server logs to find out why mid server down during discovery run and fix the mid server issue.