@Khushboo_KaliaYou can try (if not already) adding window.targetGlobalSettings logic in at.js header in Target itself i.e. under Administration > Implementation > Edit at.js Settings > Code Settings > Library Header. There's a possibility that the value is getting overridden.

@duypnguyen Thanks the complete url worked fine as the tenant. I did try it earlier as well, may be the setting might not have got deployed. Thanks again.

@michellelowsl  The content/text inside the content block is not available for validation during delivery preparation (typology rule), however if something is added before and after the content block, that could be validated. "emailContent.senderName.source" would be something like below, so you can...

@4uSwan  It could be related to how this fragment is set up. Do you face same issue with all the fragments? You can also try with very basic fragment with just a text and see if that works fine or not.

Yes I've tried with postman and I get same error like I mentioned before. I think it's mostly related to tenant as token or org gives relevant error. This is the ACS instance URL: "<some alphanumeric characters>.campaign-sandbox.adobe.com", please suggest the correct tenant id in this case though I ...

@samr99530769  To update the content programmatically, you can create a custom servlet which can take content path as input and then using QueryBuilder/ QueryManger find all the nodes under the specified path that contains the character to be superscripted.Iterate through the list of nodes and parse...

@dsomya Glad to know that you were able to resolve the issue. I've not seen any such caching issues so far, if I would change the delivery ID, atleast the error would change to reflect a new Delivery ID and not the same default ID ('DM2410'). I think we could have solved it by changing the package d...

I get the same error in logs for getProfiles() as mentioned in this post. I created a new project with template and ACS runtime action and added the tenant in .env.I have tried to debug as well though exception is thrown in the campaignClient and error does not clearly state what exactly is incorrec...

I was able to resolve this error. I went through previous publication logs to see when did this error started coming. I checked all the changes that happened in that particular publication where this error first appeared and noticed extensions in oob resource. I redrafted that resource and did anoth...

There's no straightforward way in ACS to get the Mirror Page url or email content. There's an API where you can extract the email content/ mirror page by retreiving customer history > events > Mirror page. Refer here: https://experienceleague.adobe.com/docs/campaign-standard/using/working-with-apis/...