This setting is correct for CFM. The issue is during publishing, referenced child content not publish. We need to separately publish all the child content fragment. 

Yes. I think during publishing of parent content fragment, child content fragments doesn't include in the package to publish.

I have a content fragment Model with a field of Fragment reference type. The content fragments used as a part of reference in Fragment reference field never got published when I publish the parent content fragment. I'm wondering if I'm missing something? Is there a way to publish these content used ...

Thanks @Raja_Reddy for your quick response. I'm using the on-premise version of AEM 6.5.12 and can't see method contentFragmentByPath in the documentation https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/extending/graphql-api-content-fragments. Wondering if I'm missing...

It seems interesting but somehow I was unable to use the suggested solution in my instance. I have responded with follow-up question.

@Raja_Reddy I tried to execute the above query in my AEM instance but it shows the error attached in the screenshot. Wondering if I'm missing something.I wanted to query all the content fragments available at a path along with a unique ID. Can you share the query please? 

_path returns a relative path which change after author move the content to another folder. I'm looking for some ID which should be unique and not change for a content.

Is there any unique identifier available which we can use while fetching Content Fragments content? I know AEM has jcr:UUID as a unique identifier for all content but I can't access it in the Graphql query.

Sure @kautuk_sahni. I'll share the solution with the community if find anything.

Hi @SureshDhulipudi, The publisher instance is free from authentication. From Project A, I can read all the fields of CFM created in Project A. The issue is with access to CFM B from a persistent query created in A.