Discovery stuck in starting state for long timeIssue Scheduled Discovery jobs stuck in starting state for a long period of time and start after 2 hours. Here the MID server is MID server cluster.CauseThe more ranges and the larger the number of IPs to exclude list the longer to start the Discovery.ResolutionFound the schedule which is taking longer time to start has huge list IP address exclusions. Suggest removing the exclusions list and rerunning the Discovery.