@DEBAL_DAS Thanks for the materials.They describe how to configure this service. What about details of what it does? I'm mostly interested in two things:what exactly "GREEN" status means (is it e.g. the status of some specific bundle or component?)what "Framework started" means (the same question, d...

I came to know that any AEM instance provides a web service with /systemalive path which responds with a JSON object like this:{ "systemStatus": "GREEN", "checks": [ { "check": "Framework Start Ready Check", "status": "GREEN", "details": "Framework started. Start level: 30; Target start lev...

I have found the additional source of parameters. They are configured inside Adobe Launch rules, the way it's described at https://experienceleague.adobe.com/docs/platform-learn/implement-in-websites/implement-solutions/target.html?lang=en in "Add parameters" section.

I need help to understand how Target determines what parameters to include in the /mbox/json request when getting offers. The exact issue I have seems to be caused by some legacy from people who don't work at the company anymore and left no documentation, so it's quite puzzling.When I check the requ...

Sorry for the confusion, our at.js version is actually 1.8.2.

I have managed to resolve this. In case anyone is interested, here is how it can be done:You should have a rewriter configuration in /apps/{your-site}/config/rewriter/{your-rewriter}The node's "transformerTypes" property should contain pipeline type from the configuration of the TransformerFactory t...

We are using Target loaded by Launch and consider using Target's Visual Composer with Experience Fragments exported from AEM. We also have quite a lot of components with custom JS initialization code which will be used in these fragments if we start using them.What is the recommended way of calling ...

We are considering using Target's Visual Composer with Experience Fragments exported from AEM. We also have a custom transformer Java class (extending com.adobe.acs.commons.rewriter.ContentHandlerBasedTransformer) used for some of our components' content, and those components may be included in expo...

Hi @kchaurasiya  When the issue was reproduced, we also tried clearing CDN cache. It did help for new visitors, but the ones who visited the site during the issue had the wrong file cached in their browsers already. So I would like to find the root cause of this and prevent it in future.

Hi @Fanindra_Surat  So far we have observed it on Dispatchers and CDN. We haven't yet managed to reproduce it on Publisher on intent, but apparently it does happen there: since Dispatcher has JS with a new name cached, it means it requested it from Publisher after deployment, when Publisher had alre...