JMS message - valid json but containing an unescaped right brace, job fails to submit

An automation reads a message from a JMS queue and should trigger a workspace, the message content is passed as an automation parameter. This message is valid json, however we’ve had some cases where the message is something along the lines of

{
    "ID": "1234",
    "Notes": "Careless typing} includes a right hand curly brace"
}

This is valid json but the job fails with a status of FME_FAILURE and a statusMessage of  "extra characters after close-brace".

How should the message be passed to the workspace if json like the above example leads to failure to submit?