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

Unable to handle error when the data page throws an exception

SA-72449

Summary



Unable to handle error when the data page throws an exception.


Error Messages



Caught unhandled exception: java.net.SocketTimeoutException: Read timed out


Steps to Reproduce

  1. Create a Connect-REST integration and call it from a data page
  2. Load the data page from an activity and call this activity from an agent
  3. At the activity level, check for errors in the data page by implementing a When rule whose conditional logic first tests whether the Data Page has 'messages', and then tests a value from the data page if no 'messages' exist , that is, the loading was successful
  4. Fail the Connect-REST call with an exception


Root Cause



A defect in Pegasystems' code or rules. The step status failure on invoking the connector method, Connect-REST or SOAP, in the pxCallConnector activity is not cleared. As a result, the exception is propagated to the callers.


Resolution

Perform the following local change:

Call a Rule-Utility-Function to clear the step status failure. For example, call tools.getActivityStatus().clear() through the response data transform referenced in the data page.
 



 

Published March 16, 2019 - 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