Inconsistency in Knowledge Article Workflow Field After Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I’ve noticed an inconsistency in the Knowledge Article workflow field after recent upgrade. When opening a new article form, the workflow sometimes shows as “Pending – Not Yet Started” instead of the expected “Draft.”
Has anyone else experienced this behavior?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @George_1
- Log out of your instance, clear your browser’s cookies and cache entirely, and restart your browser.
- Navigate to cache.do to flush server-side node caches.
- Review the Business Rules on the kb_knowledge table to ensure no new or updated script is prematurely attempting to push an article's workflow state into a running process
- Check whether you are getting the issue for new record or existing record.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
We recently upgraded to Australia Patch 2, and we noticed that the Workflow field behaved different, both in Classic UI and Service Operations Workspace (SOW)
It seems like all stages is set to "Not Yet Started" even though the workflow run and the stored value of workflow_state seems to be right. (Like published, draft, retired etc)
SOW:
I've raised a ticket with ServiceNow Support for this issue so I hope that they will be able to provide to insight to this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
Did u got any solution for it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
We observed the same issue and it appears to be related to the browser cache. After clearing the cache and switching to Chrome, the issue could no longer be reproduced.