CMDB Data Manager - Archive Policies failing

[JoeBaynham1]

Hi All,

We have recently implemented CMDB Data Manager in San Diego and created a few policies to start us off with, one being an archive retired servers policy. Every time an archive policy has been manually approved, the CMDBTASK updates as if it has completed but the CIs still remain in the server class. Digging into the subflow for the "Archive Configuration Items" logs, I've found that it errors out with a bunch of javascript complaints. I can upload the logs if that's helpful - was just wondering if anyone else has had similar or the same problem or any idea what might be causing archiving to fail, potentially a business rule somewhere? 

Thanks,

Joe

[JoeBaynham1]

Nope, even through multiple version upgrades, CMDB data manager seems to have gotten better (less buggy, the UI actually lets you set policies to run without needing approval etc) the out of the box policies to archive and retire CIs still continue to timeout. 

[ritikagoyal]

@mpmacconnell Are you referring to the time taken to archive CI? As a general note, archiving a CI also leads to archival of related records such as relationship records. So the time taken can depend on how many such related records need to be archived.