GraphQL Persisted Queries not available

Hi ​@RobertSHarper 
Could you please verify in your Project Configuration Browser whether the GraphQL Persisted Queries option is enabled?
 

Hi ​@RobertSHarper ,

is this still broken? Few usual suspects:

1. Tools → Configuration Browser → your config → Properties → is "GraphQL Persisted Queries" checkbox actually checked (not just the endpoint enabled)? As shown below?
2. Make sure to create the endpoint using Tools → General → GraphQL (endpoint manager). Make sure to Publish endpoint. This is the most common gotcha. AEM strictly looks for persisted queries under the exact /conf/<config-name>/... tree tied to the endpoint you selected in the dropdown — if your queries or settings sit under a different config path, the UI just ignores them. Double check that your endpoint's associated Sites configuration matches the config where you enabled persisted queries — a global endpoint vs. a site-specific endpoint pointing to different /conf paths is a frequent cause.  read this post. 
3. Does your endpoint's dropdown selection match the same /conf/<name> path where you enabled persisted queries?
4. If you manually created any persisted query nodes in CRXDE rather than through GraphiQL's "Save As" — that's a known way for AEM to silently fail to load them due to wrong JCR node types. 
5. Sometimes creating in jcr nodes might break. Make sure the path convention is /conf/<config-name>/settings/graphql/persistentQueries — if this node doesn't exist under your specific config (or was created manually with wrong node types rather than through the GraphiQL "Save As" flow), AEM can silently fail to recognize it.

#2 could be the cause.

Hi ​@RobertSHarper ,

​Adding to what's been shared, a few deeper technical edge cases to check if your /conf toggle is already enabled:

​User ACLs on /conf: Ensure your user account explicitly has Read + Write permissions under /conf/<your-project>/settings/graphql/persistentQueries. If your account lacks write access to create JCR nodes under /conf, GraphiQL won't allow query persistence.

​Dispatcher / Filter Blocks: If you are testing this on a Stage/Dev environment with a Dispatcher in front, verify your Dispatcher rules allow traffic to /graphql/execute.json and the /conf query paths. A 403 or 404 on background pre-flight requests causes the editor to display the "Not Available" warning.

​OSGi Service Configuration: Check /system/console/configMgr for GraphQLPersistedQueriesOperationServiceImpl to ensure HTTP execution methods (GET/POST) aren't restricted or misconfigured.

​AEM SDK / Local Bundle Refresh: If testing on a local SDK, try refreshing the GraphiQL client bundle or re-saving the configuration. The GraphiQL OSGi servlet sometimes caches the initial "disabled" state until a bundle refresh or instance restart occurs.