How operational / Install status life cycle update during discoveryIssue <!-- /*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: ; } } How operational / install status life cycle update during discovery? Release<!-- /*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: ; } } All Resolution<!-- /*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: ; } } In the out-of-box horizontal Discovery process, Discovery creates or updates CIs based on the discovered payload. The key field used to indicate that a CI is still being discovered is Most recent discovery / last_discovered. ServiceNow's IRE updates the CI's last_discovered and discovery_source during payload processing, even when no other CI attributes are updated. If the payload does not provide last_discovered, IRE updates it with the current timestamp. (servicenow.com) Discovery does not generally mark a CI as Retired, Terminated, or update Operational status / Install status just because the CI was not found in a discovery schedule. Those status fields are not typically managed by standard server Discovery patterns as a general retirement mechanism. Some specific pattern or class use cases may update status fields, and pattern deletion strategies can mark related CIs or configuration-file CIs as Absent or Retired, but this is not the same as a global CI lifecycle retirement process. (servicenow.com) The recommended out-of-box approach is to use CMDB Health and CMDB Data Manager together: Use CMDB Health staleness rules to identify CIs that are no longer being updated or rediscovered. Staleness rules are class-based, and a CI can be considered stale when it has not been updated within the configured effective duration. (servicenow.com) Use CMDB Data Manager to govern the lifecycle action for those stale CIs. ServiceNow documentation recommends CMDB Data Manager for creating and managing policies that automate CI lifecycle operations such as Retire, Archive, and Delete, instead of building custom cleanup logic. (servicenow.com) For retirement, configure or validate the appropriate Retirement Definition for the target CI class. An active retirement definition is required for Retire, Archive, or Delete CMDB Data Manager policies, and it defines which CI attributes are set when the CI is retired. (servicenow.com) So, the typical OOB process would be: Let Discovery continue updating last_discovered for active CIs.Define a business threshold, for example, "not discovered for 30/60/90 days."Use CMDB Health to identify stale CIs.Use CMDB Data Manager Retire policy to update the CI lifecycle/status fields in a controlled way.Optionally use approval tasks before retirement, depending on your governance process. This approach is safer than modifying Discovery patterns or creating custom business rules to directly set install_status or operational_status, because it keeps CI lifecycle changes governed, auditable, and aligned with the CMDB lifecycle framework.