So I get the same error code when I click on that data tab for nms:broadLog in my localhost and some client installs. This makes me think this is expected. What are you looking for? Do you need to see Sent, Open and Clicks of recipients?if you so you want a different table, nms:broadLogRcp or nms:tr...

To answer your question directly the through put is list in Mail Rule Sets. See below screen shot. HOWEVER, you really shouldn't need to edit this. If you have having trouble at 50K you may have other issues. I would recommend that you first start with changing the delivery priority. If you have 100...

Hi there,This looks like a custom table you created or extended. High level you should double check your data schema fields you extended.Have you updated the DB structure, logged out and logged back in? Can you share more about how you customized this table?

Was anything copied over from another workflow? The temp table of the workflow thinks that field is present. If you are 110% that field is not in existing activity (or the advance JS in activities), I would re-create that workflow from scratch in a new workflow canvas. Don't copy and past anything. ...

So looking at the code & the error again... mctx is undefined...Which means there is no data being mapped to alert.ctx.. This seems backwardsin your code you have var mctx = alert.ctx;  If you want to populate mctx with data you would need to pass something like this in your SOAP request. All variab...

So the error "content htmlContent" means that something in your HTML is not correct. Usually this is because of a personalization tag error <% %> or and If Else statement in javascript. Can you share the code you are using with mctx?

Email bots (usually) won't log into your App or website. You could always take email clickers and exclude anyone who has not logged in or authenticated on your domains.

Not sure about the preview, but the error logs clearly show the Event is not covered. Meaning the eventType you are sending to ACC does not match what is listed in the eventType enumeration. Perhaps double check those items and republish.

In the error logs this statement is failing to be evaluated "WHERE W.iRecProcState >= -1".the W.i is just SQL stuff. RecProcState is either a custom field on some custom data schema, or it is a custom expression in an enrichment or other activity within the workflow. Start by checking the update act...

I would start with verifying that RecProcState for the inbound population is all populated with the correct data type and values before the expression is evaluated. Essentially data in that field for a specific recipient is not letting the expression be evaluated. With these type of errors you have ...