we have a Stale rule as per 'class' in serviceNow . By default its 60 days can you check this . From CI class Manager under correctness you can change from 60 to 45.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful." Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect CGI M.Tech in Data Science & AI
Stale records in the ServiceNow CMDB are configuration items (CIs) that have become outdated or no longer reflect the current state of the associated IT assets. Stale records can occur due to various reasons, such as hardware or software changes that haven’t been properly updated in the CMDB.
An example of a stale record
Let’s say you have a CI representing a server in the CMDB. If that server has undergone hardware upgrades or has been decommissioned, but the CMDB still shows outdated information, such as the old hardware configuration or the server’s status as active when it’s not, then those are examples of stale records.
What are orphan records?
Orphan records in the ServiceNow CMDB are configuration items (CIs) that exist in the CMDB but are not properly related to other CIs or do not have valid relationships. Orphans can occur when CIs are created but not associated with the appropriate parent or child CIs, leading to data inconsistencies.
Example of orphan record
Imagine you have a CI representing a network switch in the CMDB. If this switch is not linked to any other CIs, like the servers or devices connected to it, or if it lacks the necessary relationships to show its place within the network topology, then it becomes an orphan record.
Both stale and orphan records can lead to inaccurate and unreliable data in the CMDB, which can affect IT asset management, change management, and incident resolution processes. It’s essential to regularly audit and clean up the CMDB to address these issues and ensure the accuracy and reliability of the data within it. ServiceNow provides tools and processes for managing and resolving these types of data quality issues.
Difference between Stale & Orphan records?
Criteria
Stale Records
Orphan Records
Definition
Outdated or inaccurate data that no longer reflects the current state of a record.
Records that exist in the system but are not properly related or connected to other records.
Example
This can lead to inaccurate decisions and confusion as the CMDB does not reflect the current state of assets.
A network switch record that is not linked to any servers or devices in the CMDB, making it isolated.
Cause
Stale records result from data becoming outdated due to changes in the real-world IT environment that were not properly updated in the system.
Orphan records are often created when records are added to the system but not associated with the correct parent or child records or lack proper relationships.
Impact
This can result in incomplete and inconsistent data, making it difficult to understand how different components are related in the IT infrastructure.
Can result in incomplete and inconsistent data, making it difficult to understand how different components are related in the IT infrastructure.
Resolution
Typically requires updating the record with correct and current information to eliminate inaccuracies.
Requires creating relationships or linking the orphan record to the appropriate parent or child records to establish data consistency.
Common Management Tool
Used by CMDB administrators and IT asset managers to maintain data accuracy.
Requires attention from CMDB administrators and data analysts to identify and establish relationships.
Examples of Resolution
Updating hardware and software information for a server in the CMDB to reflect the current state.
Associating a network switch record with the servers and devices it connects to in the CMDB.
In summary, while both stale and orphan records can lead to data quality issues in a CMDB, they have different causes and require distinct methods for resolution. Stale records involve outdated or inaccurate information, whereas orphan records involve missing or improperly linked data relationships. Resolving these issues is essential for maintaining an accurate and reliable CMDB.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful." Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect CGI M.Tech in Data Science & AI
We had the same issue a few days ago with one of our clients, and we needed to change the duration. You can go to the CMDB class member and understand how to correct it. You can then change the time to 60 days or any other value as needed. My colleague @Ravi Gaurav has also shared a screenshot for reference.
************************************************************************************************************* If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards Dr. Atul G. - Learn N Grow Together ServiceNow Techno - Functional Trainer LinkedIn: https://www.linkedin.com/in/dratulgrover YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
we have a Stale rule as per 'class' in serviceNow . By default its 60 days can you check this . From CI class Manager under correctness you can change from 60 to 45.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful." Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect CGI M.Tech in Data Science & AI
Stale records in the ServiceNow CMDB are configuration items (CIs) that have become outdated or no longer reflect the current state of the associated IT assets. Stale records can occur due to various reasons, such as hardware or software changes that haven’t been properly updated in the CMDB.
An example of a stale record
Let’s say you have a CI representing a server in the CMDB. If that server has undergone hardware upgrades or has been decommissioned, but the CMDB still shows outdated information, such as the old hardware configuration or the server’s status as active when it’s not, then those are examples of stale records.
What are orphan records?
Orphan records in the ServiceNow CMDB are configuration items (CIs) that exist in the CMDB but are not properly related to other CIs or do not have valid relationships. Orphans can occur when CIs are created but not associated with the appropriate parent or child CIs, leading to data inconsistencies.
Example of orphan record
Imagine you have a CI representing a network switch in the CMDB. If this switch is not linked to any other CIs, like the servers or devices connected to it, or if it lacks the necessary relationships to show its place within the network topology, then it becomes an orphan record.
Both stale and orphan records can lead to inaccurate and unreliable data in the CMDB, which can affect IT asset management, change management, and incident resolution processes. It’s essential to regularly audit and clean up the CMDB to address these issues and ensure the accuracy and reliability of the data within it. ServiceNow provides tools and processes for managing and resolving these types of data quality issues.
Difference between Stale & Orphan records?
Criteria
Stale Records
Orphan Records
Definition
Outdated or inaccurate data that no longer reflects the current state of a record.
Records that exist in the system but are not properly related or connected to other records.
Example
This can lead to inaccurate decisions and confusion as the CMDB does not reflect the current state of assets.
A network switch record that is not linked to any servers or devices in the CMDB, making it isolated.
Cause
Stale records result from data becoming outdated due to changes in the real-world IT environment that were not properly updated in the system.
Orphan records are often created when records are added to the system but not associated with the correct parent or child records or lack proper relationships.
Impact
This can result in incomplete and inconsistent data, making it difficult to understand how different components are related in the IT infrastructure.
Can result in incomplete and inconsistent data, making it difficult to understand how different components are related in the IT infrastructure.
Resolution
Typically requires updating the record with correct and current information to eliminate inaccuracies.
Requires creating relationships or linking the orphan record to the appropriate parent or child records to establish data consistency.
Common Management Tool
Used by CMDB administrators and IT asset managers to maintain data accuracy.
Requires attention from CMDB administrators and data analysts to identify and establish relationships.
Examples of Resolution
Updating hardware and software information for a server in the CMDB to reflect the current state.
Associating a network switch record with the servers and devices it connects to in the CMDB.
In summary, while both stale and orphan records can lead to data quality issues in a CMDB, they have different causes and require distinct methods for resolution. Stale records involve outdated or inaccurate information, whereas orphan records involve missing or improperly linked data relationships. Resolving these issues is essential for maintaining an accurate and reliable CMDB.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful." Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect CGI M.Tech in Data Science & AI
We had the same issue a few days ago with one of our clients, and we needed to change the duration. You can go to the CMDB class member and understand how to correct it. You can then change the time to 60 days or any other value as needed. My colleague @Ravi Gaurav has also shared a screenshot for reference.
************************************************************************************************************* If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards Dr. Atul G. - Learn N Grow Together ServiceNow Techno - Functional Trainer LinkedIn: https://www.linkedin.com/in/dratulgrover YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
