Discovery schedule using the wrong mid servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-11-2022 01:35 PM
I have a schedule for on prem servers that is canceling because it has gone past the max run time. In looking at the Discovery Status, Discovery is trying to use two mid servers that are not part of the cluster the schedule is pointing then to use, and those two servers are in a down state because they are in our Test instance. Why is Discovery not using the cluster and using other mids to complete the schedule?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-01-2022 10:43 AM
Thanks for your responses but the issue is resolved with the help of HI Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2025 07:38 PM
Hi Robert,
Can you help us with the Solution provided by ServiceNow Support.
Thanks