Issue when using experience fragment component on a page

[Mahesh_Kumar_Yedlapalli]

I am unable to select a variation in the experience fragment, even though I have selected a variation in the dialog. I am receiving the error message: "Choose an experience fragment variation."

Additionally, I see an API call to /content/xxx/xx/xx/en_us/xx/xx/master.3.json?_=1730751101474, but it is returning an empty response. This functionality is working fine in the environment where the API call typically returns a valid response. Can someone help me resolve this issue?

[h_kataria]

If the API call is returning empty response, then probably variations are not created properly. You can try creating a new variation just to test and try to select that. 

Also compare the content structure with the instances on which you are getting a successful response. I have observed similar cases generally where there are some missing jcr:content nodes.
Hope this helps.

[Mahesh_Kumar_Yedlapalli]

Tried different experience fragment variations but still seeing the same error. Also validated the jcr:content nodes.

[h_kataria]

Can you cross check once if your exp fragment variations have cq:xfVariantType property available or not. And share some screenshots if possible. I am on AEM 6.5.21 and the API responsible for checking the validity seems to be bin/wcm/experiencefragments/verifyreferences.json which is validating if the selected value is an actual exp fragment variation or not.

[Mahesh_Kumar_Yedlapalli]

Below is the screenshot from the environment where we are seeing this issue. Yes, cq:xfVariantType property is available.

[h_kataria]

Could you also please check the response for the API call which I mentioned i.e  /bin/wcm/experiencefragments/verifyreferences.json 
Also check if there are any cyclic references as mentioned on this thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/getting-unknown-validation... 

[Mahesh_Kumar_Yedlapalli]

I don't see any API call going for this path : /bin/wcm/experiencefragments/verifyreferences.json , Touch UI is displaying the references using a different call which is working fine.

It looks like this is not a cyclic reference issue, I don't see any issue on the page where the XF is already authored

[kautuk_sahni]

@Mahesh_Kumar_Yedlapalli Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!