Hi Rajendra, Campaign adds 'http' by default in front of the server name, there is nothing you can about it. I contacted support and this is a known bug up until build 9032. The only solution is to upgrade to at least 9036, or to install the Azure CLI and use the az commands, but I doublt that will ...

Hi @alik98709228, This can happen when your sequence (xtkNewId) has gone to its maximum value and started over at 0. Whenever that sequence catches up to the lowest ID present in your table, you will receive this error. This will be the case for ALL native tables though (with the excpetion of delive...

Hi Jon, I'm encountering the same issue as Leonie mentioned : ACC seems to only accept http connections. Do you know how to establish an https connection? Thanks !

After 1 week of waiting, 2 reminders and 1 escalation, support finally replied and fixed the issue, which was indeed related to the CNAME !

Ok great, I hope this is indeed the issue, which means an easy fix! I will update this thread whenever I get an answer from support, for future reference. Thanks for your reply!

Hello, I have the exact same issue as described in those two tickets : here and here. We implemented transactional messaging on our Staging ACS instance, where everything works fine. After moving to production, we get the following error message when calling the transaction message API. (The token e...

Hello, This feels like a really basic question, but how can we send emails to ACS users using a workflow?I tried two methods, both with a delivery using the target mapping 'mapUser' : In the first one I tried to define the audience in the delivery template itself, but once I select this delivery tem...

Hello, I'm guessing everyone who had an upgrade on their ACS instance recently noticed that the filtering in the Profiles view has changed, as described here : https://experienceleague.adobe.com/docs/campaign-standard/using/profiles-and-audiences/managing-profiles/integrated-customer-profile.html?la...

Hi Ramon, Makes sense indeed, thank you!

Hello, We're implementing transactional messaging in ACS, and have just set up the JWT Authentication in Adobe I/O. The way the encryption happens for the JWT seems strange to me, and I was wondering if anyone could help clarify this? In any other 'normal' instances, like let's say an encrypted PGP ...