Hi @djmcdermott​ , could you please share a snippet or screenshot of the errors you're getting in the job? I'm wondering if the issue is occurring at a JSON-parsing transformer and something is slightly off with a JSON query. We should be able to handle various content types in the imap_publisher_content{0} section like plain text and HTML since it's still "wrapped" in the JSON payload.

Hi @Mark Warren​ I have attached the JSON that is dropped in the Topic Monitoring. I have removed sensitive data. I think what’s happening is FME is escaping HTML characters but not CSS. For instance in this element:

<span style=\\"font-size:12.0pt;font-family:"Source Sans Pro Light",sans-serif\\">

It escapes the “ but then see’s the ; and thinks its part of the JSON. 

Thanks

Thanks for sharing the data! I've found that the errors are happening at the double-quotes (") –specifically the font-family style attributes (i.e: "Arial", "Segoe UI", "Source Sans Pro Light")–since JSON key values need to have "s escaped or else it'll be considered invalid. I used some StringReplacers to remove the double quotes from those 3 font families, and FME was able to parse the JSON after, like this:

I'm looking into this with your partner 1Spatial so we'll investigate further and share more info through the support case.

UPDATE: Using the Email Trigger in Automations and the Email Body output key avoids the issue.