HTML body property is null or empty when initiating a workflow by email


We have an xMatters workflow with an email trigger which is designed to parse the message to send an alert based on script conditions. Occasionally, the workflow fails with an empty message body even when the trigger email is complete. When we review the xMatters workflow, the input itself shows the body as empty.


All versions of xMatters


This error can occur when certain headers are included in the email. To fix this, you can remove the optional Content-Disposition header, so the receiving server renders the disposition per its configuration.

You can also check the Content-Transfer-Encoding header. If you send this, it must be set to one of these options, and avoid values like 'CHUNKED'.


Some email headers conflict with our downstream email initiating provider. 


xMatters does not necessarily endorse or support the information contained in the content linked from this article.

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.