DocumentationExperience Cloud KCS

Persisted queries unavailable in AEM GraphQL editor for non-root-level configurations

Last update: July 29, 2026

This article explains why the option to save persisted queries is unavailable in the Adobe Experience Manager (AEM) GraphQL editor when using a non-root-level configuration, and provides steps to resolve the issue.

Description description

When working with the AEM GraphQL editor, the option to save persisted queries is missing if Content Fragment Models and related settings are stored in a configuration folder that isn’t at the root level under /conf. For example, if Content Fragment Models are located in a path like /conf/dam/shared, this configuration won’t appear in the Use GraphQL schema provided by dropdown when creating a new GraphQL endpoint. Only root-level configurations that contain both Content Fragment Models and Sites/WCM settings are recognized and listed as valid endpoints. This prevents saving persisted queries for configurations that don’t meet these criteria.

Environment

  • Adobe Experience Manager (all supported versions)

Symptoms

  • The Save option for persisted queries isn’t available in the GraphQL editor.
  • The expected configuration folder doesn’t appear in the Use GraphQL schema provided by dropdown when creating a new GraphQL endpoint.
  • No specific error messages are displayed.

Cause

The AEM Sites GraphQL admin console only lists root-level configurations under /conf that contain both Content Fragment Models (settings/dam/cfm) and Sites/WCM settings (settings/wcm). Sub-configurations or folders lacking these settings aren’t recognized as valid endpoints, which prevents persisted queries from being saved.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review your current configuration structure:

    • In the AEM Configuration Browser, navigate to /libs/granite/configurations/content/view.html/conf.

    • Identify the configuration folder you are using (For example: /conf//shared).

  2. Verify configuration requirements:

    • Ensure your configuration is at the root level under /conf (For example: /conf/), not as a subfolder (such as /conf//shared).

    • Confirm the configuration contains both:

    • Content Fragment Models: settings/dam/cfm

    • Sites/WCM settings: settings/wcm (including templates, policies, or template-types)

  3. Recreate the configuration as a root-level folder:

    • Create a new root-level configuration under /conf (For example: /conf/).

    • Move or recreate your Content Fragment Models and Sites/WCM settings under this new configuration. This may involve copying the relevant nodes and settings from the subfolder to the new root-level folder using CRXDE Lite or the Configuration Browser.

  4. Update GraphQL endpoint selection:

    • Access the Sites GraphQL admin console at /libs/cq/graphql/sites/admin/content/console.html.

    • Verify that your new root-level configuration appears in the Use GraphQL schema provided by dropdown.

    • Proceed to create and save persisted queries, as needed.

  5. After completing the above steps, confirm that the Save option is now available when creating persisted queries in the GraphQL editor.

recommendation-more-help
experience-cloud-kcs-help-kbarticles