deduplication remediation of ci let to deletion of all ci instead of merging

[dick linschoten]

Hi we ran some deduplication remediation but for some it resulted that both involved ci where deleted instead of merged. 
does any one have an Idea on what might cause this?
that way we can try to prevent it to happen in the future

[Chetna_dev]

If both CIs were deleted instead of merged during deduplication, potential causes  include:

Possible Causes

1. Incorrect Matching Logic: Broad or poorly defined criteria could lead to false positives.
2. Misconfigured Merge Rules: Rules may default to deletion under certain conditions.
3. Data Integrity Issues: Conflicting or incomplete data might hinder proper merging.
4. User Error: Manual actions during the process could result in accidental deletions.
5. Workflow Errors: Bugs in automation scripts could lead to unintended outcomes.
6. Lack of Backup: Without backups, deleted CIs cannot be restored.

if you found this helpful please accept as solution and mark helpful

best

Chetna

[dick linschoten · Accepted solution]

I ran in to this https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0753605 artikle on the topic.
luckily we our non prod instance had still the data in so i validated the case here was that
ci A pointed to an asset and that asset pointed to CI B
so here when ci A was merged to ci B it cascade delete the Asset and the deletion of the asset cascade deleted CI B