Hi @Deleted Account - what is the error you are getting?We found there is a bug with the activity where you have to edit the schema after a delivery to remove @broadlog-id as this causes the AAM activity to error out.Cheers Darren

Hi @ukender - try using a directive for MSO at the end of your style block to define the fontyou want to use. Have a look at this: https://litmus.com/community/discussions/6286-web-fonts-in-outlook-woff-or-otf

The proof targets are random substitution emails. I have tried recreating the delivery from scratch only copying the HTML and Text part across and the same issue happens. What is strange, is if we create a new workflow from scratch on Stage, the issue doesnt seem to happen

Hi @Ramaswami - try adding a final else{} statement to your else if{}<%if ( dataSource.Job_Category =="Corporate" ) { %>1<% } else if ( dataSource.Job_Category =="Call Center") {%>2<% } else {} %>  

Hi @ukender - Microsoft Outlook is a pain on many levels. You usually have to use the !important style tag on custom fonts to get them to stick in MSO.https://help.sharpspring.com/hc/en-us/articles/115002203011-Why-Emails-Render-Differently-in-Microsoft-OutlookCheers Darren

We have a weird issue that when we try to proof a delivery on our Staging instance, and select "Enable proof sending" in the Approvals, the target population drops to zero when there are non-zero amount of targets. There are no targets being removed by typologies (I removed all typologies), duplicat...

Hi @sarrankanp50398 - there is a bit more to setting your application servers up for redundancy. I would suggest you have a look at a typical setup that involves application  server redundancy and you will get an idea of what is involved: https://docs.adobe.com/content/help/en/campaign-classic/using...

https://docs.adobe.com/content/help/en/campaign-classic/using/monitoring-campaign-classic/production-procedures/usual-commands.html

If you have a on-premise installation of ACC and have access to the server command-line then it will be nlserver start <module>@<INSTANCE> If your instance is Adobe-hosted then you need to contact support to start the module for you

You will need to be an administrator usually but click on Home > Monitoring then look for sms@<instance_name> in the Processes List. Then click "Open the log journal" and you will see the service logs for the sms process. Look for any error messages for the SMPP process