AEM 6.5.19 – GraphQL Persistent Query Index Limited to 50 Content Fragment Models

[Shiv_Prakash_Patel]

I’m facing an issue in AEM 6.5.19 where only the first 50 Content Fragment Models (CFMs) are indexed and available for GraphQL persistent queries.

My project currently includes 53 CFMs, but the last 3 models are not indexed after a Maven-based deployment. As a temporary workaround, I manually publish the missing CFMs, which triggers their indexing. However, this solution is not sustainable, as the issue reappears after every deployment.

Has anyone else encountered this limitation? Is there a way to configure AEM to index all CFMs (more than 50) automatically after deployment? Any suggestions or proven solutions would be appreciated.

[SantoshSai]

Hi @Shiv_Prakash_Patel,

May I know what is the version of GraphQL Index Package are you using?

[SantoshSai]

I think, this is a known issue in AEM 6.5.x versions, including AEM 6.5.19, where only the first 50 Content Fragment Models (CFMs) are indexed for GraphQL persistent queries. This limitation is due to a hardcoded pagination limit in the internal CFM indexing logic.

I found Adobe's official acknowledgement - recommends installing the Content Fragment with GraphQL Index Definition Package to fix GraphQL indexing issues in AEM 6.5.x. This is documented in the following sources:

“Customers using GraphQL should install the AEM Content Fragment with GraphQL Index Package 1.0.5.”
Link: https://experienceleague.adobe.com/docs/experience-manager-65-lts/content/assets/extending/graphql-a...

Also, there is community discussion on similar topic: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-5-13-known-issue-whi...

So, I would recommend to install the package cfm-graphql-index-def-1.0.5.zip as this package should updates the indexing configuration to ensure all CFMs are properly indexed for GraphQL.

Hope this helps!