Discovery Schedule Issue

[abhisingh]

Hi i am facing issue with Discovery Schedule, Discovery Status is showing cancelled and it's started and completed number (output and input) are not the same, please help me what could be the possibilities if output and input are not the same, what are the process to debug this.

[Chuck Tomasi]

Hi Abhi,

The first step is to take a look at the Discovery log entries that go with that. Open up the schedule and see if you can determine where the discovery scheduled stopped. If you can find that, you may be able to find out why.

[abhisingh]

Thanks Chuck, for your quick response and what i found in logs is "Canceling discovery because max run time window has been exceeded".   So one doubt i have -- for which schedule this error msg is coming yesterday that schedule has been completed successfully today, i did not get this point..means if Max Run Time is creating an issue so this issue have to come everyday but some day it is getting completed successfully and some time it's get canceled please help why this is happening.

[Sashi K1]

below thread may be useful

Re: Trouble with Max Run Time Discovery Schedule Parameter

[top_tanti]

The discovery schedule is being cancelled because the max run time window is being exceeded. It could be as simple as your max run time window is set too low. If your window is set to 10 hours and your schedule takes approximately 9.5-10.5 to complete, there's enough fluctuation to cause the discovery to be cancelled on some days and not others.

What is the max run time window for this particular schedule?

When the schedule completes successfully, how long does it take?

How/when is the schedule configured? Daily? Periodically?