Stale CI Dashboard Includes Retired CIs<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Question: Why are retired CIs still showing up in the CMDB Staleness Dashboard? Answer: This usually occurs because the CMDB Health staleness logic evaluates last updated dates rather than CI lifecycle states. Retired CIs may still be included if the health inclusion rules or system properties don’t explicitly filter them out. Troubleshooting Steps: Verify the Health Inclusion Rules in CMDB Health. Retired CIs will continue to show if they are not excluded here. Review the five CMDB Health jobs (Audit, Completeness, Staleness, Orphans, Duplicates). Confirm they are enabled and run without errors. Look in the System Logs for errors when the staleness job executes.