Discovery schedules configured to run as after discovery are not getting triggered

[Rinkus]

Hello Experts,

We have observed lately that our discovery schedules that are configured to run as after discovery are not getting triggered immediately after their parent schedule is completed/cancelled. Next schedule takes around 20-30 mins to trigger after its previous schedule gets completed.

Already validated the MID server status during schedules execution and even if cancel is active.

Anyone has faced similar issue?

Thanks in advance!

Rinku

[pratiksha5]

Is it happening in the cloud discovery VM schedule? 

[Rinkus]

Hi Pratiksha,

On-prem VMs and Network device schedules. It's just random schedule.

Thanks

[pratiksha5]

Please share the log screenshot.

[Rinkus]

Which log screenshot do you need? 

Thanks