What happens if "run after" discovery schedule is inactive?

[Jason Wright]

In our environment, many of the schedules are set to run after one another to avoid overloading the MID server at any given time:

Sched A > Sched B > Sched C

However, there is often a need to deactivate a schedule that is no longer is use.  Does anyone happen to know if there is a mechanism in place to skip to the next "run after" (from A to C, if B is inactive), or do I need to manually adjust this each time we deactivate a discovery schedule?

[Niklas Peterson · Accepted solution]

Hi,

No, if C is set to run after B and B is inactive then C will not run since B did not run. You need to move the dependency of C from B to A if you want to run C after A.

Regards,
Niklas

[Pratiksha]

If you do have schedules in a lot of number then I would say that run the schedule and check how much time it is taking. According to that schedule the next one. ( This is you need to per mid server only once)