Discovery - Devices Stuck in Classified or Identifying Status Due to Missing Identifier Entry on Identification Rule<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; max-width: 100%; } .kb-wrapper h2 { font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 28px; margin-bottom: 12px; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 0; padding-left: 24px; } .kb-wrapper li { margin-bottom: 6px; } .kb-wrapper code { font-family: 'Courier New', monospace; font-size: 11pt; background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 16px 0; font-size: 12pt; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 16px 0; font-size: 12pt; } .kb-wrapper .related-links-list { list-style: none; padding-left: 0; } .kb-wrapper .related-links-list li { margin-bottom: 10px; } .kb-wrapper .link-disclaimer { font-size: 10pt; font-style: italic; color: #444; display: block; margin-top: 2px; } .kb-wrapper ol.steps-list { list-style: none; counter-reset: steps-counter; padding-left: 0; margin: 0 0 16px 0; } .kb-wrapper ol.steps-list li { counter-increment: steps-counter; display: flex; align-items: flex-start; gap: 12px; margin-bottom: 10px; } .kb-wrapper ol.steps-list li::before { content: counter(steps-counter); background: #032D42; color: #63DF4E; font-weight: 900; font-size: 11pt; min-width: 26px; height: 26px; border-radius: 50%; display: flex; align-items: center; justify-content: center; flex-shrink: 0; margin-top: 2px; } .kb-wrapper ol.steps-list li .step-body { flex: 1; } .kb-wrapper table { border-collapse: collapse; width: 100%; margin-bottom: 16px; font-size: 12pt; } .kb-wrapper table th { background: #032D42; color: #ffffff; padding: 8px 12px; text-align: left; } .kb-wrapper table td { padding: 8px 12px; border: 1px solid #ccc; } .kb-wrapper table tr:nth-child(even) td { background: #e8fce4; } Issue Devices are stuck in a Classified or Identifying status following a Discovery run. Pattern logs contain an error similar to the following: identification sections in pattern failed: section: discovery, error: Relation and/or reference table cmdb_serial_number is not a known CI Type. Check the discovery logs for more details The table name referenced in the error message corresponds to the CI Type value of a missing Identifier Entry on the applicable Identification Rule. While this article uses cmdb_serial_number as the example, the same error pattern applies to any CI Type or Identifier Entry that has been removed. Symptoms Discovery completes but devices remain in a Classified or Identifying state on the Devices related list of the Discovery Status record, and are not promoted to the CMDB.Pattern logs contain the error: Relation and/or reference table [table_name] is not a known CI TypeThe Discovery log references a failure in the identification section of a pattern. Facts This issue is caused by a missing or removed Identifier Entry on an Identification Rule — in this example, the Serial Number Identifier Entry (cmdb_serial_number) on the Hardware Identification Rule.The Identification and Reconciliation Engine (IRE) relies on Identifier Entries to resolve CI Types during pattern execution. If an expected Identifier Entry is absent, the identification section of the pattern fails.Identifier Entries are part of the base system configuration delivered with the relevant plugin. Customer modifications that remove these entries — intentionally or inadvertently — are not automatically restored by platform upgrades.The table referenced in the error message identifies which Identifier Entry is missing from the Identification Rule. Release All Versions Cause The out-of-box (OOB) Identifier Entry for the affected CI Type (in this example, Serial Number — cmdb_serial_number) was removed from the Hardware Identification Rule by a customer update. Without this Identifier Entry, the IRE cannot resolve the referenced CI Type during pattern execution, causing the identification section to fail and leaving devices in a Classified or Identifying state on the Devices related list of the Discovery Status record. Resolution Use the appropriate method below based on the current state of the Identifier Entry record. Option 1 — Revert the record to Base System (if the record was modified but not deleted) Navigate to the Identification Rule containing the affected Identifier Entry (for example, the Hardware Identification Rule). Locate the Identifier Entry for the affected CI Type (for example, cmdb_serial_number). Open the record and use the context menu or History to revert it to the Base System version. Save the record and re-run Discovery to confirm devices are now identified and promoted correctly. Option 2 — Restore from the Deleted Records table (if the record was deleted) Navigate to sys_metadata_delete.list in the application navigator. Search for the deleted Identifier Entry record by name or table name (for example, cmdb_serial_number). If the record is found, restore it using the Restore UI action. Re-run Discovery to confirm the issue is resolved. Note: If the record is not found in the sys_metadata_delete table, the deletion may predate the instance's metadata delete history. Proceed to Option 3. Option 3 — Repair the plugin (if the record cannot be found in the Deleted Records table) Navigate to System Definition > Plugins. Locate the plugin that delivers the affected Identification Rule and Identifier Entry. For the Hardware Identification Rule and Serial Number Identifier Entry, this is the CMDB CI Class Models plugin (com.snc.cmdb.models). Click on the plugin and use the Repair option to restore all base system files delivered by that plugin, including the missing Identifier Entry. Re-run Discovery to confirm devices are now identified and promoted correctly. Important: Repairing a plugin restores all base system files delivered by that plugin. Review any customizations in scope before proceeding, as local modifications to records delivered by the plugin may be overwritten. Related Links CMDB Identification and Reconciliation