DocumentationExperience Cloud KCS

AEMaaCS: /conf folder missing from Templates UI grid despite existing in repository

Last update: August 5, 2026

In Adobe Experience Manager as a Cloud Service, a configuration folder under /conf doesn’t appear in the Templates Console even though the content exists in the repository and opens through a direct Templates URL. This issue affects template folder visibility for authors in specific environments. To fix this, verify the folder content and permissions with supported tools, compare behavior across environments, and review index-related changes through deployment.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Adobe Experience Manager Sites
  • Templates Console in affected author environments

Issue/Symptoms

  • You don’t see a configuration folder under /conf/<folder-name> in the Templates Console grid at templates.html/conf in affected author environments.
  • The folder exists in the repository at /conf/<folder-name>/settings/wcm/templates as a cq:Page and contains multiple templates.
  • The folder opens correctly when you navigate directly to templates.html/conf/<folder-name>.
  • The same folder appears correctly in other author environments.
  • Permissions are aligned with working configurations and include jcr:read for the required users.
  • XPath and query debugging confirm that the node exists in all environments.
  • Packaging and redeploying the folder doesn’t change the behavior.
  • No error message appears in the UI. The issue is limited to the folder card not appearing in the main Templates Console grid.

Resolution resolution

To fix this issue, follow these steps:

  1. Open the Templates Console at templates.html/conf and confirm that the folder is missing from the main grid.

  2. Open the folder directly at templates.html/conf/<folder-name> and confirm that the templates load.

  3. Use Repository Browser to verify that /conf/<folder-name>/settings/wcm/templatesexists and contains the expected template nodes.

    • Confirm that the folder exists as a cq:Page.
    • Confirm that the expected templates are present under the folder.

  4. Compare the affected author environment with a working author environment.

    • Verify that the folder structure matches.
    • Verify that the access control entries match, including jcr:read where required.
    • Verify that the same content package or code deployment is present.
    • Confirm that XPath and query debugging return the same node in both environments.

  5. Review recent index-related changes for the affected environment.

    • Check whether template discovery depends on a custom page index.
    • Check whether recent index definition changes were deployed successfully.
    • Allow indexing to complete after deployment before you recheck the Templates Console.
    • Note: In Adobe Experience Manager as a Cloud Service, manage index changes through deployment instead of changing /oak:index properties on a running cloud environment.

  6. Refresh the Templates Console at templates.html/confand verify that the folder appears.

    • If the folder still opens through the direct URL but remains missing from the grid, the issue is limited to template folder discovery in the UI.

  7. If the folder still doesn’t appear, contact Adobe Support.

    • Provide the affected folder path under /conf.
    • Provide the affected author environments.
    • Provide query or explain-plan evidence.
    • Confirm that direct folder access works while the Templates Console grid omits the folder.
recommendation-more-help
experience-cloud-kcs-help-kbarticles