ServiceNow Discovery Getting Stuck in the “Identifying” Phase

[amarkhade]

Hi everyone,
I’m running Discovery for the first time on a new ServiceNow instance, and I’m running into an issue where the process gets stuck at the Identification phase.

In the Discovery log I consistently see the message:
“Classified, now Identifying”
…but it never moves forward from there.

Has anyone encountered this before or can suggest what I should check?
So far, I’ve verified the MID Server is up and validated, and credentials are configured, but the scan still doesn’t progress beyond the Identification step.

Any guidance or troubleshooting steps would be really appreciated.
Thanks!

[Bhavani Shankar]

Hey @amarkhade,

I assume the discovery stops after the classification phase and patterns or not triggered. If that is the case, I would suggest you check the discovery classification config (from discovery_classy_windows.LIST) and see in the "Trigger probes" related list whether the probe that needs to be triggered is active.

Select the correct classification record since there are multiple for Windows.

If this is not the case, I can suggest better with a snapshot of the classification input payload.