Discovery Status stuck and stays in 'Starting ' state for Discovery Schedule.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-25-2019 08:15 AM
Discovery Status stays in 'Starting ' state for Discovery Schedule.
But when i ran quick discovery, it is started and completed successfully.
- Labels:
-
Orchestration

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2019 06:17 PM
My guess is that one of the MID Servers is stuck and probably needs to be bounced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2019 06:32 PM
Can you share more about your discovery schedule?
Do you have mid servers selected and are up?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-23-2020 09:45 PM
hi,
Issue was resolved? I am facing the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2022 07:49 PM
I'm having the same challenge. It is stuck in "starting" after launching by script. The schedule that is being passed to discoverySchedule has a cluster of five mid servers assigned.