Hi, we're seeing an issue with client build 9342 connecting to server build 9032. Is there a compatibility issue here? 

We used an update process to change ID values of event configurations. This was done to avoid deleting and recreating them. We changed the value from EVT<various text values> to something like '1707211'. That process worked, but after that we are no longer able to publish, we get an error of attribu...

Thanks, we have come to the same conclusion. We are also fairly certain that this is likely not what the client will want to do at this point and they would use fatigue rules to simply prevent the same profile from receiving more than 3 emails in a day.

Right, fatigue is against the recipient level, but we are looking for an overall cap. For instance, no more than 3 specific deliveries to be sent on a certain day, even if 8 deliveries are submitted. Is there a way to have the tool automatically hold 5 of the deliveries from being sent that day?

I see the document for ACC has details for capacity rules, but what about ACS? Is there only the option for fatigue, which would be at the recipient level and not an overall email send cap per day? I have a request to cap the amount of unique deliveries being sent per day. Before we go down a differ...

The issue has been resolved. The problem was the "Do not import recipients into the database" dialog box was checked. We couldn't uncheck it, that was the only difference between the production instance and the sandbox I was comparing it to. To fix it, we changed the value in the delivery form from ...

Correct, I set up a workflow to fail (no logic in a query) so we could see the alert to make sure it works. Now that I'm taking a closer look at this instance compared to another, I see a working instance has Population from a file in the To line and this non-working instance has a specific set of e...

Thanks for the reply. This is for the pre-configured alert on a workflow failure (notifySupervisor technical delivery template), there isn't a notification activity in the workflow itself to actual configure. In the workflow properties this is set for the failure notice. Any pre-configured template ...

I see the document for ACC around capacity, but what about ACS? Is there only the option for fatigue, which would be at the recipient level and not an overall email send cap per day?

When we try to use the OOTB notification of workflow supervisor we encounter delivery errors, specifically:Error while compiling script 'content htmlContent' line 6: dataSource is not defined. SCR-160012 JavaScript: error while evaluating script 'content htmlContent'.Trying to preview the delivery t...