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]

When you run the discovery schedule in the status the first tab is log.

[Rinkus]

Attached are the logs for completed discovery schedule. Next schedule which is supposed to run after this schedule has not triggered. Sometimes it takes around an hour to trigger.

[pratiksha5]

Try this : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0689001#:~:text=%22Run%20Afte....