Troubleshooting ServiceNow HR Knowledge Management: A Practical Guide

This page helps HR knowledge owners diagnose why employees cannot find or use knowledge articles in ServiceNow. Each symptom is matched to where to look first, its likely causes, the fixes to try and when to escalate to ServiceNow support or the implementation team.

Symptom: Knowledge Base Searches Return No Results or Irrelevant Articles

Employees search for common terms and see no articles, or the wrong articles rank first. The knowledge base exists but is not usable for employees.

Where to look: Check the search index status in the Knowledge Management settings. Verify that articles are published and set to visible for external users. Review the search ranking rules and synonyms configuration. Check article tags and keywords to confirm they match employee search terms.

Likely causes: The search index has not been rebuilt since articles were published. Articles are created but not published. Search tagging was done with HR terminology rather than employee terminology. Synonyms were not configured for common search variations (e.g., “PTO” and “time off” should be synonyms).

Fixes: Manually rebuild the search index or wait for the scheduled rebuild to complete. Verify articles are marked Published and set to External visibility. Audit the top 10 employee searches and confirm the results are relevant; rerank or retag articles as needed. Add synonyms for common search variations.

When to escalate: If the search index is corrupt or the search feature is not working at all, contact ServiceNow support. If you have custom search configurations, escalate to your implementation team to review the configuration.

Symptom: Employee Portal Does Not Display Knowledge Articles

Employees browse the self-service portal but do not see knowledge articles. The knowledge base exists in ServiceNow but is not integrated with the customer-facing portal.

Where to look: Check the portal configuration to verify the knowledge widget is enabled and configured. Verify that articles are published and marked for external visibility. Check article categories to confirm they are assigned and visible in the portal.

Likely causes: The knowledge widget was not added to the portal during implementation. Articles are created but marked as internal-only visibility. Article categories or metadata are missing, so the portal cannot organize and display them.

Fixes: If the knowledge widget is missing from the portal, add it and configure it to display articles relevant to the current context. For articles marked as internal-only, change the visibility setting to external. Audit articles and populate missing metadata so they display correctly in the portal.

When to escalate: If the portal framework is not working or the knowledge widget has errors, escalate to your portal team or ServiceNow support.

Symptom: Search Performance is Slow or Queries Timeout

Employees search the knowledge base and see slow results or timeouts. The knowledge base contains too many articles or the search index is too large.

Where to look: Check the Knowledge Management configuration for search index settings. Review the database query logs to identify slow queries. Check article counts and categorization to understand the scale of the knowledge base.

Likely causes: The search index has grown very large and needs optimization. Search queries are written to search all article content instead of indexed fields. The database has insufficient performance tuning for the volume of searches.

Fixes: Optimize the search index by archiving old articles that are no longer relevant. Configure search to use indexed fields rather than full-text search where possible. Review the search configuration with your implementation team and consider tuning database indexes or adding caching.

When to escalate: If search performance remains slow after optimization, escalate to your database administrator or ServiceNow support for performance tuning.

Symptom: Articles Are Out of Date or Inaccurate

Employees report that article content does not match current policy or process. Articles reference old system versions or discontinued products. Trust in the knowledge base erodes.

Where to look: Review recent articles for accuracy. Check the article creation and modification dates to identify which articles have not been reviewed recently. Review high-traffic articles first, as outdated popular articles cause the most damage.

Likely causes: No process exists to review and update articles regularly. When policies change, the knowledge base is not updated. Article authors do not have ownership for ongoing maintenance.

Fixes: Assign content owners for each HR topic area. Schedule article reviews and include them in staff responsibilities. When a policy or process changes, immediately update related articles. Archive or retire articles that are no longer relevant.

When to escalate: Establish a governance process with HR leadership to assign ownership for article maintenance and define review cycles.

Symptom: Low Knowledge Base Adoption or Employees Keep Opening Cases

The knowledge base exists but employees do not use it. Case volume has not decreased since the knowledge base was implemented.

Where to look: Check knowledge base usage analytics. Review search volume and which articles get the most views. Compare this to case topics to identify gaps between employee questions and available knowledge.

Likely causes: Employees do not know the knowledge base exists. Articles are available but do not answer the questions employees are asking. Case workflows do not surface knowledge articles to employees. HR staff do not promote self-service.

Fixes: Promote the knowledge base through multiple channels: email announcements, portal banners, and HR website links. Review top case topics and ensure you have knowledge articles addressing them. Update case workflows to surface relevant articles before accepting a case. Train HR staff to respond to cases by pointing to knowledge articles.

When to escalate: If adoption remains low after promotion and content improvements, consider a training or change management campaign with HR leadership.

Start by finding out who is affected

When an employee reports that an article is missing or wrong, the first question is not what broke. It is who is affected. A problem seen by one employee in one department points toward restriction or an audience setting. A problem seen by everyone points toward publication state, indexing or the portal widget. A problem seen only on phones points toward layout or a mobile-specific setting. Narrowing the population first saves effort that would otherwise go into rebuilding a search index that was never the cause.

1. Ask the reporter for their role, their location and the device they used, and the exact words they typed.
2. Reproduce the search with a test account of the same role, then with an administrator account, and compare the results.
3. If the admin account finds the article and the employee account does not, the cause is access, not content.
4. If both accounts find it but the portal does not show it, check the widget and the category assignment.
5. Only when every account sees the same stale result should indexing or ranking be investigated.

Matching the symptom to the first check

Each symptom has a most likely cause and a first check that rules it in or out. The table below is organized by what the employee sees, since that is the description support teams will receive.

Recognizing the misdiagnoses that waste the most time

Three misdiagnoses recur. The first is blaming search for what is really a restriction, as above. The second is a browser cache effect, where a corrected article still shows the old text on one device because the employee’s session has not refreshed. Asking the employee to reload with a private window can clear this quickly and avoid a platform ticket. Where the same pattern shows up on the case side, the HR case management troubleshooting guide covers symptom recognition for cases. The third is treating a low rating as a technical fault. A low rating is a content signal, and the fix belongs with whoever writes the article, not with the platform team. The HR knowledge management best practices guide covers how knowledge is organized around the employee journey.

When to stop troubleshooting and redesign

Some recurring problems are a sign that the structure is wrong, not that a setting is off. If the same topic keeps returning no results after the synonyms have been added, the taxonomy may be built around HR terminology that employees never use. If every fix to one article creates a problem in a related one, the articles are probably duplicates. At that point a targeted redesign of the category or the article set is cheaper than a long run of individual repairs, and it is worth raising with the governance owner. The HR knowledge management overview describes what the module covers.

Questions employees and support staff ask about these problems

Why does a colleague see an article I cannot find?

Often because of audience or role restriction. Ask the colleague for their role, then compare it with yours. Restriction is designed to hide content, so the mismatch is expected and not a fault.

Why does the result order change between desktop and mobile?

The search may be applying different filters or display rules on each device. Check that both use the same article set and the same audience, and record any difference that remains as a known limitation.

Will archiving old articles make search faster?

It can reduce the number of candidates a search has to rank, but it is not a fix for a slow platform. Confirm the cause in the performance logs before archiving content that employees may still need.

What should a support agent tell an employee while the fix is in progress?

Give the employee the answer from the policy owner directly, with a note that the article is being corrected. That keeps the employee moving and stops the same question being logged as a new case.