Article moving from Published to Reviewed, then back to Published.Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms An article is published in the KB. Someone will go in, click edit and make changes to the KB. The changes the article back to review status whereby the KB approve is unable to re-publish the KB. It is stuck in review status and grey out Resolution This behavior is due to a custom business rule. This business rule is setting the workflow back to review. The current out of box workflows being used are not designed for the workflow to move back to review from published. This is why the approval process is not firing. In an out of box instance, when a record is edited, it stays published and does not move back to reviewed. If you would like to keep this implementation, the workflows would have to be customized to send back out the approval process. If you were to disable this business rule, this would likely work the same as an out of box instance. An article only moves to Retired or pending retirement from Published. The article will remain in the published state after it is edited. If you would like an approval process to take place after a change is made a customization would be needed. The other possibility would be to enable the article versioning feature. Any time a published article is edited, a new version of the record is created. This new version would then go through the approval process (if approval publish workflow is set) and the original version would then be set to 'Outdated'. Additional Information Article versioning https://docs.servicenow.com/csh?topicname=article-versioning.html&version=latest