Hi @kautuk_sahni ,Unfortunately not yet. I will share once I have found the solution.Thanks

Hi @Raja_Reddy ,1. Which configuration specifically do you want me to check? Make sure that it is correctly configured to point to the language-specific folder for the experience fragment - Which configuration you mean by this?2. No error that could lead to this3. With new XF, this issue doesn't exi...

Hi @SureshDhulipudi ,This is the scenario when XF is created already for all 4 languages. When I create the language copy of page, then the path pf XF is not right, as I mentioned. I didn't understand your second question?

Hi @salamswapnil Thank you for your response. This looks more like when Live Copy is used. We are not creating live copies, but rather only language copies. Does that still apply? BR,Rupal 

Hi All,  We are using AEM Cloud solution to build our website. We have built custom components and used them as experience fragments. Scenario - 1. I create a page in master language and use an experience fragment in that page.2. I create language copy of that page in 3 other languages.3. When I ope...

Hi @EstebanBustamante , Yes, in the end I found this out and then it was successful. Thank you for replying to my question Its weird that Adobe documentation is not clear enough for this.  Best,Rupal

Hi @Saravanan_Dharmaraj ,Thank you. I will check this too. But were you able to see Adobe Target in cloud configurations in Experience fragments Properties Tab like here ?For me, the problem is that it doesn't appear here and hence everything fails after that. 

Hi Ravi, Yes, I have configured Adobe Target as per Experience League documentation. Below is the error log :02.10.2023 00:09:56.537 [cm-p91922-e816739-aem-author-748f7d7ff5-bj77q] *WARN* [sling-cq-polling-importer-10-/conf/<my-app>/settings/cloudconfigs/target] com.day.cq.polling.importer.impl.Poll...

Hi Everyone,We are using AEM as Clouse service for our website and I have integrated Adobe Target and Adobe Launch as Cloud Service. I configure A/B Testing and it works fine, so the configuration is done correctly.However, when I am trying to export Experience Fragment to Adobe Target, it throws er...