The Operational field was not getting automatically to retire after the Yokohama upgrade

[ShravaniV]

In the Service now earlier, the Operational field was getting updated automatically to Retired but we noticed that after the Service Now new version upgrade which is Yokohama, this change is not happening, we have to manually make the changes and retire it.

[Vikram Reddy · Accepted solution]

Hi @ShravaniV,

It's a Retirement Definition that got reset or deactivated during the upgrade. The automatic flip of Operational status to Retired on a CI is driven by CI Lifecycle Management in CMDB Data Manager, not by a hardcoded platform rule, so it's exactly the kind of config that can silently drop when definitions get reverted to OOB defaults. Worth checking:

• Under CMDB Data Manager, whether the Retirement Definition for the relevant CI class (or the parent cmdb_ci definition it inherits) is still Active
• Which field that definition actually targets, since OOB defaults to life_cycle_stage, not operational_status, someone may have swapped it previously and the upgrade reverted it
• Whether the retirement scheduled job or policy that runs the definition is still active and running on schedule
• Whether a custom Business Rule or Flow was doing this instead, and got deactivated as part of the upgrade's skip/customization review

If you can confirm which of these it is (or share the CI class), happy to narrow it down further.

References

• Retire Configuration Items Subflow not updating Operational Status to retired
• CI Lifecycle Management (Yokohama)

Thank you,
Vikram Karety
Octigo Solutions INC

[ShravaniV]

Thank you for the response.