ServiceNow Discovery Cancelled With Reason: No progress was detected on status. Cancel status

[omkarsave]

Hi Team,

Our ServiceNow Discovery Cancelled With Reason: No progress was detected on status. Cancel status

Logs showing below error

Discovery decision Cancel
Reason: No progress was detected on status. Cancel status

We have verified the Mid Server logs but still didn't find any failed reason

[RGreene]

I am seeing the same issue.  It seems Yokohama is a bit cancel happy.  I have a bunch of slow to respond devices.  With Xanadu on this one schedule, it would discover 274 devices and now with Yokohama it is consistently canceling the schedule with only 193 discovered.

I wonder if there are any controls (System Properties) for this behavior.

[ashishmitta]

Same issue in our environment. Most of Discovery schedules gets automatic cancelled with No detailed logs!

Looks like, some bug in Yokohama version and ServiceNow needs to fix it on priority. 

[Yo der Einfache]

Hello,

we have the same problem. If you choose Quick-Discovery or you start it direct from a server, it seems that Discovery is working very slowly but it is working. Starting Discovery from a schedule it will cancelled.

[Joe125]

Same issue here - Only SNMP Discovery for our UPS's seem to be effected.
Doesn't matter if entire Discovery Schedule or single IP for quick Discovery.

Am raising a case also.

[MDAQUIBK]

@omkarsave  Did you get any resolution for the issue . I am also facing the same issue.