@alex_bundschuh thank you very much for your valued input!Error in the first place was the PIP07 scenario specific outbound processing, where a content modifier step failed due to an XPath error (because no payload available).Pipeline Generic Step01 ...
We activated the integrated messaging runtime and use it for a high load use case (>100.000 proxy messages per day).We have used this scenario with PIP configuration already before without integrated runtime and everything went smooth. With the usage...
Hi,
take a look at note 2768991 - Parsing exception during custom result handling.
Setting the parameter "skipCustomResultConversion" solved this for me.
Best regards,
Ronald
