- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2026 12:05 PM
Changing category on published article creates new version but old version stays active under old category
Questions:
1. Is this expected behavior when changing category on a versioned published article, or did the supersede fail to complete?
2. Why are Outdated versions still appearing in the Knowledge Search category facet — is this an indexing/reindex issue?
3. What’s the recommended OOTB way to clean up ~100+ affected articles so only the new-category version remains?
Any guidance appreciated — happy to share more config detail.
has context menu
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2026 12:25 PM
Hi @emiltalley
OOB once you publish KB , a new version will be created and old version would be outdated.
KB0778944 Outdated version of the article is still visible to the end users
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2026 12:25 PM
Hi @emiltalley
OOB once you publish KB , a new version will be created and old version would be outdated.
KB0778944 Outdated version of the article is still visible to the end users
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2026 01:14 PM
When a published versioned article is edited and the Category is changed:
- ServiceNow creates a new version (expected).
- The previous version is transitioned to Outdated (expected).
- The new version becomes Published (expected).
However...
The previous version should not normally be returned in end-user search if:
- Search filters exclude outdated articles.
- Search index is updated correctly.
- The Knowledge Search source filters only latest published versions.