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

Existing requestor retrieved message and Pega0069 Alerts



Slow performance is observed in Pega applications.

The Alert log analysis for Pega0069 suggests a passivation issue since the last input shows 'existing requestor retrieved' message for almost every one of these Alerts.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

A defect in Pegasystems’ code or rules.

Pega0069 alerts are created on the NEXT http interaction - not on the one that exceeded the threshold. The next http interaction will send in the Client times from the browser.

So that may factor into how this "existing requestor retrieved" message is placed in the alert.

​Pega will investigate what we want to do with the last input message in 0069 alerts, as it isn't clear if anything in the subsequent http request is relevant to the prior request that tripped the alert.


Bug-311189 has been entered for this to be looked at in a future release of Pega.

Suggest Edit

Published August 16, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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