Hi Community,
I created a Data Manager policy to retire Unmatched CIs and Unclassed Hardware. When I reviewed the policy preview, it showed approximately 50k records, which matches the number returned when I run the same query directly against our CMDB.
However, only about 30k CIs were retired, and these were only the Unclassed Hardware records. The Unmatched CIs remain in an Operational status.
I then created a separate policy specifically for Unmatched CIs, but the result was the same. I even created a policy targeting a single CI from the Unmatched CI class, but it still was not retired.
I do not think the issue is related to the subflow or the retirement definitions, as we only have a single retirement definition for the cmdb_ci table (and OOB).
Has anyone experienced something similar or knows what could be causing this behavior?
Thanks in advance!
