Thanks fsiegel, looks like we had a lack of communication internally. That is exactly the same event that was wreaking havoc in this
thread and eventually to support case # 00044477. We had to replace the blob for the event due to an incorrectly parsed character. Should I bring it up with support again?