My app invokes the SOAP API to send transactional messages using a triggered send and a SendLog data extension. To track the status of messages, I use query activities to join the Send, Open, and Bounce data views with the SendLog data extension. Occasionally, sends that are accepted in the send API call fail during the actual send. Those sends never end up in any of the data views, but they end up in the SendLog data extension with an ErrorCode > 0.
Is there any way to get more detail about why these sends have failed? The error codes are fairly broad, making it difficult to provide feedback to end-users. I'm able to get detailed bounce information using the _Bounce data view, but these sends never get to that point.
Here's the reference page for the send error codes – http://help.exacttarget.com/en/documentation/exacttarget/content/email_messages/email_send_error_codes/
The types of errors I'm seeing are ErrorCode=20 which has the name "Invalid Field Value" and the description "The value specified for a data extension field does not match the field type". Is there any way to know which field?
Likewise, I'm seeing ErrorCode=24 which has the name "List Detective Exclusion" and the description "The subscriber was excluded by List Detective." I'd like to know why the subscriber was excluded.
Best Answer
Details about these things are generally scant. SFMC Support and certain partners have access to a server error log. Sometimes it will give you insights into Data Extension field value errors.
I doubt you'll get much info on List Detective exclusions. It's the secret sauce/spam trap blacklist the SFMC uses. It may be worth a call to SFMC Support to see what they say.
There's also a Not Sent Tracking Extract and the canned Subscribers Not Sent Report that'll give you some more of this info.