Unable to retire a knowledge blockDescriptionThe user tried to retire a Knowledge Block but was unable to. They keep getting an error message that says, "Block cannot be retired as it is currently being used in other articles." While this is a documented behavior, the user does not even have the option to disassociate a Knowledge Article from a Knowledge Block. This is the issue.CauseThis is documented in PRB1547677. Unfortunately, this Problem record was closed as Working as Expected. This is not the case (and as such, has been addressed with Development), and the user should be informed that while the design is intended, the feature to disassociate the Knowledge Article from the Knowledge Block is currently (as of San Diego) not implemented. Therefore, the documentation is made moot.ResolutionDiscussing the above with the Knowledge Management Developers at ServiceNow, a workaround was provided until the permanent fix which will come in the Tokyo family release. The workaround is only capable of preventing authors from associating Knowledge Blocks with more articles. This does not sever the association of the Knowledge Block with articles where the relationship exists already (there is no way to do this, currently). The workaround is the below script, which will deactivate the Knowledge Block. Once again, this was provided directly as the only viable "workaround" from ServiceNow Knowledge Management Developers: var gr = new GlideRecord ('kb_knowledge_block');gr.get('sysIdOfKnowledgeBlockHere');gr.active = 'false';gr.update();