Scheduled Discovery getting canceled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2022 06:14 AM
Hi everyone
Scheduled Discovery is getting canceled with error "Canceling discovery because max run time window has been exceeded".
We tried to increase the max run time of the schedule, but still the schedule goes up to that run time set & gets canceled.
When we try to run the schedule with "Discover now" option- it works fine. Scheduled discovery is causing this issue.
Does anyone have any idea why this scenario could happen?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2022 06:32 AM
How long does it take for a successful discovery?
And what is the max run time?
Maybe discovery is scheduled during a backup.
So target servers are busy at that time, or the MID Server(s) are busy with other things during discovery.
Check the performance of the MID servers during the scheduled time.
Regards,
Michael
Michael
Please mark the suggestion as helpful/like, if you find it useful to you or others who wants to refer similar content.
Please mark the solution as correct, if the answer provided has resolved your query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2022 06:34 AM
See this support article:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0692463
Kindly mark help and mark as correct answer if it helps in resolving your issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2023 08:32 AM
Hello
I am not able to see that KB, can you please provide me access to it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2023 09:42 AM
We had same issue and I was able to find the workaround/solution for it.
Resolution# VM schedule should automatically pick up the subnets from OCI cloud Subnets table and added those subnets to VM schedule. but that’s not happening now.
Workaround# go to Cloud Subnets (cmdb_ci_cloud_subnet) table there must be subnets discovered by cloud, export those manually and added those subnets into VM schedule, then run VM schedule job.
Hope this help, if so please mark it to Helpful / Accept this solution. Thank you in Advance.
Regards,
Vinil.
