Discovery updating the old decommissioned Non operational status CI Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery updating the Non-operational Lifecycle status CI ( old decommissioned ) even though identification inclusion rule in place.When you have identification inclusion rule for cmdb_ci table in place to include only operational CIs for the identification process, the new CI should not match on any of the CIs with Life Cycle status non-operational and should create a new CI, but this does not happen here. Cause Identification inclusion rule is not working because the instance is using legacy CI identifier rule Resolution Set sys_property "glide.discovery.use_cmdb_identifiers" to true, to switch to new CI identification rule.Then, identification and reconciliation will be handled by the CMDB API instead of through the old Discovery implementation. Additional Information Related Errors and troubleshooting articles: KB0723079 - CMDB Identification Error: Missing mandatory field KB0720501 - CMDB Identification Error: In payload invalid data source [Manual Entry] exist