CMDB Data Manager Attestation how it Identify records to incluced in Task

[pbels1]

Current work with the Attestation Policy in CMDB Data Manager

• The poicy I create is to create for Attesting to CI if the install_status is not Retired (this is on for testing)
• When I can the Policy the first time it woiuld as expected
• Found out that if a CI is part of a Attestion task it will not create a new task
• So I canceled one of the task
• All the records in 'sn_cmdb_ws_attestation_task_to_ci'  where delete from the table
• So I expected that the next run of the policy wouild create a task with the records that where the task I canceled
• On the next run of the policy job no task where create

What are the rules that are used in the are used in the policy job to Identify CI to have tasks created.

[KPNow]

When the CMDB Data Manager policy job runs, it doesn't just evaluate your raw filter condition (install_status != Retired); it passes CIs through several exclusion checks to prevent duplicate work and spamming task assignees. First, it filters out CIs listed in the CMDB Policy Exclusion table (cmdb_policy_ci_exclusion_list) or those that belong to an active exclusion definition. Next, it checks existing tasks in cmdb_data_manager_taskalongside policy execution logs. Crucially, the engine factors in the attestation frequency/interval configured on your policy (e.g., monthly, quarterly). Even if you clear the mapping records from sn_cmdb_ws_attestation_task_to_ci, the underlying policy execution history or task execution record still registers that those CIs were already evaluated during the current policy window cycle.

Because simply canceling a task or deleting its task-to-CI mapping rows does not reset the policy's execution audit state, the policy engine considers those CIs "already processed" for the current run cycle. To force the engine to generate a new task for those target CIs on the next run, you need to either cancel or delete the parent CMDB Data Manager Task record itself (in cmdb_data_manager_task), clear or reset the policy's execution audit history for those target CIs, or adjust the attestation frequency schedule/date window on the policy so the engine views them as due for a new evaluation cycle.