de-duplication task are closed skipped after detecting the duplicate ci in cmdb please why its dir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi there @tejamma
This means no remediation is required anymore. This happenss if the duplicate CI was already resolved, marked as a duplicate or handled automatically by CMDB remediation logic.
i suggest you to check the task's Activity Log, Work Notes, and Updated By fields which will give u clear idea on wyhy.
Kind Regards,
Azar
Serivenow Rising Star ⭐
Developer @ KPMG.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @tejamma
The IRE does not process duplicate CIs if either of the following conditions is true:
- The glide.identification_engine.skip_duplicates property is set to false.
- The number of duplicates found exceeds the maximum threshold defined by the glide.identification_engine.skip_duplicates.threshold property (default value: 5).
Refer KB: KB0750386 How the CMDB Identification and Reconciliation Engine processes a CI payload
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
yes with all below setting and system properties skip duplicate is true and default value 5 even though the state of the de-duplicate task is open in developer instance but in my instance its showing as closed skipped.
i want state of the de-duplication task should be open so whenever correctness job ran then this duplicate ci should as shown CMDB correctness dashboard in duplicate tab.