By two projects I mean conf/A and conf/B. When I create a persistent query in A, I can't read the fields of CFM created in B.

Yes, the query is working fine if I create the persistent query in A and try to read the CFM fields created in A. The issue is only when we try to read CFM created in B from a persistent query created in A.

Yes, the query is working fine if I create the persistent query in A and try to read the CFM fields created in A. The issue is only when we try to read CFM created in B from a persistent query created in A.

We created one reusable Content Fragment Model (CFM) in a common project(A) and tried to reuse it in another project(B). While trying to read the Content Fragment Model field of A using a persistent query created inside B, it shows an error message like below:Wondering if anyone faced the similar pr...

I think I figure out the issue. To share with everyone correct query is:query productList($productID:String,$locale:String) {productList(filter:{ productID : {_expressions: [{value:$productID}]}}, _locale : $locale ) {items{ flag { ... on ProductFlagModel{title,backgroundColor,flagColor...

Hi @krati_garg , I have updated the question to add the required details.

I have a content fragment model having a single-valued field of type Fragment reference, in which 2 Content Fragment models are allowed.I am looking into the most effective approach to write a Graphql query handling both content fragment models within a single field. Our initial attempt encompassed ...

@aanchal-sikka , I can see this issue with all the CFM. It was working before and I'm having Administrator rights and was able to publish CFM before and can publish in other environments. I have updated the question to include error log message.

Thanks, @Suraj_Kamdi . I have updated the question to attach the log message.

Seems an error message indicates a missing segment. As I'm still not able to understand the root cause of failing publishing so attached the log message in the question so that anyone can suggest a fix in case seen a similar issue.