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

Poor performance with connector



Users experience extremely slow performance.

Error Messages

PegaRULES-ALERT log shows Pega0001 (slow user interaction) with KPI of 10,000 or higher (milliseconds) for affected users.

Steps to Reproduce

Not Applicable

Root Cause

A third-party issue is the cause of this problem.  Further analysis of the ALERT log shows Pega0020 with similar KPI on the same requestor ID, indicating a slow external service connection.

Looking at the PAL stats provided in the alert (example)

This is the number of milliseconds for the external service connection - 1 millisecond to map the outgoing response, over 30 seconds to receive a response from the external client, and 2 milliseconds to map the incoming response to corresponding pega properties.


The external service is the cause of the slow performance.  This issue must be addressed by the provider of the external service.


Published February 9, 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