Hi,  Did some more digging, according to yaml.org this seems to be a limitation: http://yaml.org/spec/1.2/spec.html#id2795688 “…Inside literal scalars, all (indented) characters are considered to be content, including white space characters. Note that all line break characters are normalized. In addition, empty lines are not folded, though final line breaks and trailing empty lines are chomped. There is no way to escape characters inside literal scalars. This restricts them to printable characters. In addition, there is no way to break a long literal line. [171] l-nb-literal-text(n) ::= l-empty(n,block-in)* s-indent(n) nb-char+ [172] b-nb-literal-next(n) ::= b-as-line-feed l-nb-literal-text(n) [173] l-literal-content(n,t) ::= ( l-nb-literal-text(n) b-nb-literal-next(n)*   b-chomped-last(t) )? l-chomped-empty(n,t)   Tried using “\” but this breaks the logmonitor: “…[Agent-Monitor-Scheduler-4] 17 Aug 2017 10:34:32,506 ERROR LogMonitor - Unfortunately an issue has occurred: while scanning a quoted scalar in 'reader', line 24, column 19:              pattern: '<ns0\:ResultMsgCode>.*?</ns0\:R ...                       ^ found the unexpected end of stream in 'reader', line 44, column 1:…” Tried it in single quotes as well as no quotes and this chops the rest of the string off as it does with double-quotes. Replacing special characters seems to be the best method, many thanks for your assistance Satish 🙂 Regards, Dean ... View more