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

.pyQueryTimeoutInterval not changing timeout settings



Using the properties Code-Pega-List.pyQueryTimeoutInterval and Rule-System-Setting pyQueryTimeoutInterval does not make a difference with RDB- rules or Report Definitions.

Error Messages

There was a problem getting a list: code: 0 SQLState: 08006 Message: An I/O error occurred while sending to the backend.

Steps to Reproduce

1) Change .pyQueryTimeoutInterval in Rule-System-Setting or step page of Code-Pega-List or RDB List/Open/Save
2) Run rule
3) Timeout always occurs at 90s not to any value of .pyQueryTimeoutInterval

Root Cause

A defect or configuration issue in the operating environment: Network socket timeout was set to 90 seconds in the environment.


Make the following change to the operating environment: Return socket timeout to default value, and/or a value high enough to allow reports to run successfully.

Published August 26, 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