try setting NmsMidSourcing_LogsPeriodHour to 1 hour, restart workflow after that change by doing "Unconditional stop" first and then start it again. When using FDA over HTTPs connection, the Mid-sourcing (delivery logs) (defaultMidSourcingLog) workflow was stuck in the timeframe set by the NmsMidSou...

Did you find a solution?

Post the DNS errors here, raise a ticket to Adobe Support as a P3 as they have a better chance at troubleshooting any throughput issues, perhaps there is a bottleneck/limitation somewhere.

You have a better chance at contacting Adobe Support and raise it as a P1 It seems you have system A trying to communicate with system B and there is an issue where the request is being dropped. The HTTP query returned a 'Internal Server Error' type error (500) (iRc=-53)Seems like an access rights/ ...

That's an error with the MTA (Mail Transfer Agent) for email deliverability, if you have a hybrid solution, the MTAs will be on the Adobe cloud solution, so that is perhaps why is not configured on your on-premise marketing, try setting the following config-<instancename>.xml<mta autoStart="true" st...

You won't be able to edit a delivery which has already been sent at this point, you need to make the changes to the template not the delivery.

gpg --batch --passphrase passphrase --decrypt <%=vars.filename%>  Try this guidehttps://experienceleague.adobe.com/docs/campaign-classic/using/getting-started/importing-and-exporting-data/managing-data-encryption-compression/zip-encrypt.html?lang=en#use-case-gpg-encrypt Check this thread out (standa...

<% if (targetData.segmentCode =='H' ) { %> 20% <% } else if (targetData.segmentCode =='M' ) { %> 30% <% } else if (targetData.segmentCode =='L' ) { %> 40% <%}%>If you want to preview, choose a seed, then add segmentCode to seed's additional data   

Nice point to consider @Darren_Bowers I will bring this up to my client, did you develop the solution at the end? have you thought about the processes to revert changes? custom schema? maybe a webapp sends command to workflow to fetch the user's before changes from temp schema and revert? I am looki...

This option was introduced in the build below, you have to create it and set it to 1, after that you will see debug messages on the workflow, after you are done, set it back to 0Release 19.1 - Build 9026{#release-19-1-build-9026}