Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connect SOAP throwing exception while consuming external Service



Connect SOAP in PRPC 6.2 SP2 based application throws an exception due to “actions mismatch” while consuming SOAP Service.

Error Messages

com.pega.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch)
at com.pega.apache.rampart.handler.WSDoAllReceiver.processBasic(

Steps to Reproduce

Connect to an external SOAP Service using Connect SOAP rule with WS-Security enabled.

Root Cause

The root cause of this issue was “Timestamp” not mentioned in Inflow of Security Profile. The response received from the external SOAP Service had Timestamp in the security header.


Adding Timestamp in Inflow of Security Profile resolved the issue.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us