This could be caused by a few things:
- The xpath query [1] used by the AEM Client Library Manager (HTMLLibraryManager) is using some index other than the /oak:index/nodetype index.
- The nodetype index is failing to get updated or is corrupted.
- The clientlibs-service user's permissions are missing.
[1]
/jcr:root//element(*, cq:ClientLibraryFolder)
I. Check the service user permissions
Review this article in case the clientlibs-service user permissions are missing.
-
Validate whether or not your missing client library is in the results. If it there then contact AEM Customer Care to get help with further investigation. Otherwise continue to the next step.
-
You would need to debug what is causing a different index to return a lower cost estimation for the query. Refer to this article for how to enable debug logging for query analysis.
-
Follow the steps in this article to reindex the index asynchronously.