Hi @KevinD691869774 ,
As per my understanding why CIs might not be retiring:
1. Retirement Policy vs Retirement Definition
* The Policy (screenshot 1) identifies which CIs should be retired (e.g., Installed + Operational + last discovery before Feb 2025).
* The Definition (screenshot 2) defines how those CIs are marked retired (e.g., change Install Status → Retired and Operational Status → Non-Operational).
2. If these are not linked correctly or if only the attestation/retirement task is created but Definition is not triggered, the CI will not update.
3. Execution Mode
* By default, CMDB Data Manager can be set to just create review tasks (manual step required) or to auto-update the CI.
* If your config is only creating tasks, then unless the task is completed/approved, the CI record won’t be updated.
4. CI Class Coverage
* The Policy seems applied on a generic class (Install Status & Operational Status exist on most CIs), but your Definition screenshot is scoped only to Fibre Channel Disk.
* If the stale CIs are in another table (like cmdb_ci_computer or cmdb_ci_win_server), the Definition won’t fire.
5. Permissions / Data Manager Jobs
* Ensure the CMDB Data Manager job is active and has permission to update the CIs.
* Check the Retirement Job logs (cmdb_data_management_job table) to confirm if the Definition was applied after task creation.
Steps to Fix which might helpful.
1. Verify Policy-Definition Linkage
* In your Policy record → check the Retirement Definitions related list. Make sure your Fibre Channel Disk definition is attached there.
* If you want multiple classes to retire, create additional definitions per class.
2. Change Policy Behavior (if needed)
* If you don’t want manual task approval, set the policy to auto-retire CIs. Otherwise, ensure tasks are being closed properly (which then triggers the CI update).
3. Run in Preview Mode First
* Use Preview Policy Execution in CMDB Data Manager → confirm which CIs qualify.
* Check if those CIs appear in the Definition execution logs.
4. Check CI Update
* After job runs, open a CI record and verify if Install Status = Retired and Operational Status = Non-Operational are being set.
* If not, look at sys_execution_tracker logs for errors.
Final Expected State:
* Stale CIs will be automatically updated with:
* Install Status = Retired
* Operational Status = Non-Operational
* If tasks are enabled, you’ll see attestation tasks that when completed will trigger the updates.
* CMDB stays cleaner without manual intervention for each CI.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025
