AEM GraphQL fails on one folder after an index migration

A GraphQL endpoint can be configured correctly and still fail on one Content Fragment folder. In a recent Experience League thread, Author queries began returning an endpoint error after an index migration, while other folders using the same model worked. The poster confirmed a query-read or traversal-limit message in logs. That evidence points toward query execution and candidate-set size, not a missing endpoint.

Reproduce the exact failing query

Save the query, variables, environment, affected folder, request time, and corresponding Author log entry. Run the same query against a small unaffected folder and a bounded sample from the affected one. Compare the fragment counts for the model across the repository, not just the final result size. Adobe’s GraphQL optimization guide explains that a small output can still be expensive when many fragments are loaded before filtering.

Prove the index path

Review index health after the deployment and use the query performance or explain tools to inspect the actual index selected. Adobe’s query and indexing guidance distinguishes index traversal from final result size. A matching index definition on disk is not proof that the active query plan uses it. Keep the explain output before and after any index change. Do not raise traversal limits or exclude a large folder merely to make one query pass without assessing other consumers.

Reduce the initial candidate set

Where the query permits it, filter on top-level fragment fields and use bounded pagination. Adobe documents hybrid filtering and first/after paging for this purpose, with limitations for nested filters and sorting. Test changes in a lower environment using representative content volume and the same query variables. If the plan is correct yet the read limit persists, take the query, explain output, index health, and log trace to Adobe Support.

Adovo’s view

An endpoint error is only the last symptom in a content query. The real contract is that a specific customer experience can find the right fragment within a predictable resource budget. Diagnose that contract at the query and index boundary before changing infrastructure or masking the failure with cache.