Troubleshooting Benchmarks errors
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Troubleshooting Benchmarks errors
This guide helps ServiceNow customers identify and resolve common issues encountered when setting up or running Benchmarks in the Yokohama release. It focuses on troubleshooting data errors that affect dashboard visibility, data collection, and score generation.
Show less
Common Data Error Scenarios and Actions
- No data in dashboard after opting in: This can result from a failed download REST API for six months or connection failure. Verify the event
snbmclient.download.scores.6monthsis processed in thesyseventtable. - No instance data for the last month: Caused by Performance Analytics (PA) data collection or scorecards API failure. Check KPI indicator source conditions and ensure historical data collection jobs for the KPI have a state of Collected in Platform Analytics > Data Collector > Jobs.
- No global or cohort benchmark scores for the last month: May be due to download REST API failure or insufficient customer participation (minimum 10 customers per cohort). Verify the event
snbmclient.download.scoresis processed and cohort participation meets minimum requirements. - Opt-in process failure: Typically caused by authentication failure or unsupported instance type. Contact Customer Service and Support for assistance.
- Incorrect or missing KPI data in Benchmarks dashboard: Check KPI definitions and conditions in Performance Analytics > Sources > Indicator Sources. Ensure at least one to two months (recommended 60 days) of aggregated historical KPI data is available.
- No data in Percentile Rank list view: Occurs if viewing an industry outside your cohort or if insufficient cohort participation exists. Confirm your industry inclusion and that cohorts have at least 10 customers.
- No data in Top Performer score: Happens when minimum historical KPI data is unavailable. Confirm availability of one to two months of aggregated monthly KPI data (recommended 60 days).
Practical Implications
Following these verification steps ensures accurate and complete data is available in Benchmarks dashboards, enabling reliable performance insights and comparisons. Monitoring event processing, data collection job statuses, cohort participation thresholds, and KPI data sufficiency are key to maintaining Benchmark data integrity.
Troubleshoot and resolve common errors when setting up or running Benchmarks.
| Scenario | Reason | Action |
|---|---|---|
| No data in dashboard after opting in. | The download REST API for six months failed or there is a connection failure. | Verify in the sysevent table that the sn_bm_client.download.scores.6months event is processed. |
| No instance data is shown in the dashboard for the last month. | PA data collection or scorecards API failure. |
|
| No global or cohort benchmark scores in dashboard for the last month. |
|
|
| Opt-in process fails. | Authentication failed or the instance type is not supported. | Contact Customer Service and Support team. |
| Incorrect or no KPI data in the Benchmarks dashboard. |
|
|
| No data in Percentile Rank list view. | Percentile Rank shows N/A due to the following reasons.
|
|
| No data in Top Performer score. | Top Performer score shows N/A if the minimum historical data scores for KPIs are not available. | Make sure that a minimum of one to two months of aggregate monthly historical data for a KPI is available. The recommended time interval is 60 days. |