CMDB Lifecycle Issue: CI showing Installed but Operational Status = Non-Operational – How to debug

[NagaLakshmiC376]

I am trying to identify the root cause of this mismatch and understand what is driving these status updates. Context: - Environment: ServiceNow Discovery / CMDB - CI Classes: (e.g., Computer, Cloud Service Account,

Hi Team,

I am working on CMDB lifecycle status analysis, and I am facing an issue where multiple Configuration Items (CIs) are showing: - Install Status = Installed - Operational Status = Non-Operational

Servers, etc.) - Volume: ~ (mention count, e.g., 200+ or 400+ CIs) - Discovery is running regularly, but statuses are not aligned Problem: Even though the CI is marked as "Installed", the "Operational Status" is set to "Non-Operational", and I want to understand: 1. What processes update Operational Status? 2. Is this driven by Discovery, patterns, business rules, or lifecycle mappings? 3. How can I trace what is changing the status? What I have checked: - CI history and audit logs - Discovery status and last discovered timestamps - Basic lifecycle mapping What I am looking for: - Step-by-step debugging approach - Common root causes for Installed / Non-Operational mismatch - Tables / logs / scripts to trace status updates - Best practices to prevent this issue If anyone has faced a similar issue or can guide on how to debug this effectively, that would be very helpful.

Thanks in advance!

[pr8172510]

Hi @NagaLakshmiC376,

 Install Status and Operational Status are independent fields and are not automatically synchronized.

Therefore, a CI can legitimately haveInstall Status = Installed Operational
Status = Non-Operational

 source of the update:

1. Check Audit History (sys_audit) for changes to operational_status.
2. Review Discovery logs and the CI's Last Discovered timestamp.
3. Check for Business Rules, Flow Designer flows, Scheduled Jobs, or integrations updating the CI.
4. Review any CMDB Lifecycle Management configurations affecting Operational Status.

ServiceNow Discovery primarily identifies and updates CI data, but Operational Status can also be driven by lifecycle processes, integrations, or custom logic.
The most reliable way to find the root cause is to trace the update through Audit History and system logs.

[NagaLakshmiC376]

Thank You