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 troubleshoot common errors encountered when setting up or running Benchmarks in the Xanadu release. It focuses on diagnosing data availability issues, API failures, and configuration problems that affect the display and accuracy of benchmark dashboards and scores.
Show less
Common Error Scenarios and Actions
- No data in dashboard after opting in: This occurs if the six-month download REST API fails or there is a connection issue. Verify processing of the
snbmclient.download.scores.6monthsevent in thesyseventtable. - No instance data shown for the last month: Often caused by Performance Analytics (PA) data collection or scorecard API failures. Check the indicator source conditions and ensure monthly historical data collection jobs are in the "Collected" state under Platform Analytics > Data Collector > Jobs.
- No global or cohort benchmark scores for the last month: Can result from REST API failures or insufficient customer participation (minimum 10 customers per cohort required). Validate the
snbmclient.download.scoresevent processing and cohort sizes. - Opt-in process fails: Typically due to authentication issues or unsupported instance types. Contact Customer Service and Support for resolution.
- Incorrect or no KPI data in Benchmarks dashboard: Verify KPI definitions and conditions in Performance Analytics > Sources > Indicator Sources. Ensure at least 1-2 months (recommended 60 days) of aggregate monthly historical data is available.
- No data in Percentile Rank list view: Occurs when viewing industries outside your participation or when cohorts lack sufficient customers (minimum 10). Confirm your industry inclusion and cohort sizes.
- No data in Top Performer score: Happens if minimum historical KPI data is unavailable. Ensure 1-2 months of aggregate monthly KPI data exists, with 60 days recommended.
Practical Benefits
By following these troubleshooting steps, customers can quickly identify data and configuration issues impacting Benchmarks dashboards and scores. This ensures accurate performance insights, reliable benchmarking, and smoother opt-in experiences, enabling better data-driven decision-making.
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. |