Discovery status is FAILURE

[Community Alums]

Hi Team,

Created customized Application pattern for one of the host and in the debug mode the patterns are successfully, but after i run the discovery against the host, its showing below error:

"Identification Engine: Discovery status is FAILURE, Discovery using patterns failed due to lack of existence of the main CI type in the results. Check the discovery logs for more details."

what could be the reason? and i checked all possibilities.

Any help is appreciated!

Thanks in advance!

[danielherre]

Hi Community!

might also be late on this reply, but as long as I got stuck here during Discovery Fundamentals On Demand training, what helped me was to make sure that the application for which we want to create a pattern, has a corresponding configuration item (CI) in the defined table, (cmdb_ci_appl). In my case, I was missing it, and was getting this same error message: "Discovery status is FAILURE, Discovery using patterns failed due to lack of existence of the main CI type in the results. Check the discovery logs for more details.", I guess main CI type is about this.
Hope it helps 🙂

[sanketpatil09]

The error means that during Discovery your custom application pattern is not creating the main CI that ServiceNow expects. In debug mode, patterns can look successful because the steps run, but when Discovery runs fully, the Identification Engine checks whether the root CI (the class you set as the main CI type in your pattern) is actually created and has the required fields. If that CI is missing, or if the mandatory identification fields like name, host, or install path are not filled, Discovery fails with this message. This usually happens if the pattern does not include a Create step for the main CI, or if the wrong class is chosen as the root CI type. It can also happen if classification does not match the host properly. To fix it, check that your pattern has the correct root CI type, includes a Create step for that CI, and fills the required identification attributes. After that, clear logs and rerun the Discovery — the main CI should then be created successfully.