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

Data Page throwing ConnectorException propagates FAIL to callers



Data Page load using Connect-SOAP does not handle the external system exception gracefully if there is a SOAP failure.

This application requirement is that checking all the data pages before loading the portal.

Error handling is implemented using a data transform and referring all the data pages.

If there is a failure in one of the data pages load, then it is handled gracefully.

Unfortunately application error handling logic is not triggered if there is a Connect-SOAP failure during data page load.

Error Messages

Soap Service failed exception

Steps to Reproduce

1. Force data page load issue through connect-soap failure.
2. Handle the exception in data pages.

Root Cause

Closer look at the exception indicates that failure is triggered by 'IndeterminateConditionalException' in a 'When' rule, which resulted the reported behavior.

Pega code change is made to handle this exception.


Apply HFix-33671.

Published April 25, 2017 - 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