CMDB Health Dashboard Correctness Scorecard Max failure Error

[MohammadAmzad]

Hi Everyone, I have configured Staleness rule, however i am not able to see correct scorecard, its showing maximum failure, please refer the below screenshots i am on Yokohama patch-4 please help me to configure correctness scorecard.

[Abbas_5]

Hello @MohammadAmzad,

Please refer to the below link:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1123059

If it is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution it will be helpful to them.

Thanks & Regards,

Abbas Shaik

[AJ-TechTrek]

Hi @MohammadAmzad ,

As per my understanding, You can follow below steps:-

1. Review the staleness rule configuration
* Go to Data Certification > Correctness > Staleness Rules (or via CMDB Health → Correctness).
* Verify:
* The query behind the staleness rule is valid and correctly scoped.
* The time frame / threshold (e.g., last discovered > X days) makes sense for the CI classes you’re evaluating.
* Ensure you don't have too strict thresholds that cause most CIs to fail.

2. Check if the staleness job is running successfully
* Navigate to:
cmdb_health_staleness_job.list
* Confirm the job execution status is completed and not failed.
* Look for any errors in:
* System Logs → All
* cmdb_health_staleness_log.list

3. Evaluate the evaluated CIs
* Check if the staleness rule is evaluating the correct CI classes.
* Make sure the CIs actually have the fields used in the staleness rule (like Last Discovered).

4. Adjust the rule or data if needed
* If your environment really has many outdated CIs, consider:
* Extending the freshness threshold in the rule.
* Running Discovery to update the Last Discovered date.
* Sometimes after initial config, the data is actually stale, so the rule is correct in reporting failures.

5. Use the CMDB Health Dashboard troubleshooting tools
* Go to CMDB Workspace > Completeness/Correctness.
* Drill into the staleness rule, click More options (…) → View records to see exactly which CIs are failing.
* This helps validate if it’s a rule misconfiguration or genuine data quality issue.

6. Recalculate correctness
After fixing:
* Go to CMDB Health > Correctness > Recalculate Correctness.
* Trigger a fresh calculation to reflect the changes.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025