Hi @prakharbt20 ,
Based on the latest screenshot, Discovery does not appear to be stuck. The Discovery Log shows "Discovery completed" immediately after the "Classified, now Identifying" message.
The more likely issue is that Discovery successfully classified the Windows device but was unable to create or identify a CI, which is why the CMDB CI field remains empty.
I would recommend reviewing the output of the Windows OS – Desktops pattern and checking the Identification Engine (IRE) logs to confirm whether the required identifier attributes (such as hostname, serial number, or UUID) were collected. Missing identifier values can prevent ServiceNow from creating or matching a CI even though the discovery itself completes successfully.
Also verify whether any errors are reported in Discovery Errors Home and review the Pattern Launcher ECC payload for additional details.
Hope this helps.
