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

Response Timeout on Connect-REST



User is having an external Rest service which takes longer time to respond (5mins). In this case, user wants to know the impact of keeping the response time-out attribute to 5mins on the Connect-REST rule form.

Requested for the below information -

What is the ideal value for setting the Response Time-out ? Any side effects ?
or any other alternation suggestions ?


The explanation for this behavior is as follows: 

1. Response Timeout value (milliseconds) is just a threshold value like "when do I give up?"

2. It is a best practise to have threshold value not more than 1-2 mins.

3. If your external rest service taking up longer time to respond, let’s say 5 mins, it is not that advisable to keep response timeout value to 5 mins, as the user just have to wait for 5 mins on the same screen. (Consider fine-tuning the REST service).

4. In the above case (5mins) there might be a chance of getting a thread hung as the thread will go into the activity code and will have to wait on that.

5. On your screens, consider using data pages where you can source it from Connect-REST service and define your refresh strategies to load the data when required. 

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