Archive Policy creates CMDBTASK records that are immediately removed (0 tasks persist)Issue A CMDB Data Manager Archive Policy reports matching a large number of CIs on each scheduled run, but no archive tasks persist — either 0 tasks are created, or CMDBTASK records appear briefly and are then automatically removed on the same run. The matched CIs are never actually archived. Facts An Archive Policy that matches records but produces zero persisting archive tasks, or creates CMDBTASK records that vanish on the same run, is most likely blocked by an ACL on the target CI table that doesn't grant DataManager Job Runner the roles it needs to read those CIs. Confirming the service account's read access and adding the missing role resolves it. Release ALL Cause CMDB Data Manager policies execute as the out-of-box service account DataManager Job Runner, not as the user who created or triggered the policy. If a legacy or overly restrictive ACL on the CI table being archived (for example, cmdb_ci_vm_object) does not grant DataManager Job Runner the roles it needs to read the target CIs, the job cannot actually read any of the matched records. With no readable CI data to act on, every CI is skipped and any task created for it is immediately removed rather than retained — so the policy reports matching thousands of records but silently does nothing with them. This can look like a "Needs review" gating or "Managed By Group" approver-routing configuration problem (both were investigated and ruled out in the source case), when the real blocker is upstream: the service account cannot read the data at all, so there's nothing for the review/approval gate to act on either. Resolution Confirm the symptom: the policy reports matching N records, but 0 tasks persist, or tasks appear and are removed on the same run.Rule out approval-gate causes first: confirm "Needs review" and "Managed By Group" are configured as intended (populated with qualifying approvers). If tasks still don't persist with these correctly configured, the cause is upstream of the approval gate.Impersonate the DataManager Job Runner service account (or run an equivalent script as that user) and attempt to read a sample of the matched CIs directly. If read access is denied, this confirms the service account cannot see the target records.Review the ACL(s) on the CI table in question (e.g., cmdb_ci_vm_object) for required roles that DataManager Job Runner does not currently hold.Per KB2718202, add the required role (for example, itil or asset) to the DataManager Job Runner user so it can read the target CIs. Review this role addition with your licensing/security team before applying it, since it changes a service account's access scope.Re-trigger the Archive Policy and confirm tasks are now created, persist, and have CIs correctly linked to them. Validate the fix in a non-production instance first, then apply the same role change to production and re-run the policy there to confirm the same behavior.