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

Getting PEGA0005 alerts due to OOTB activities/rules at runtime



In the application alert logs file , most of the PEGA0005 alerts are generating due to OOTB standard pega rules like (pr4_rules and other tables) while getting data from the pega DB. 

Error Messages

Alerts in Pega Alert log file.

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment, behaviour was initially reported with Pega0005 alerts with an impression as this be the root cause for the slowness. However by going through alert logs, Pega0037 was the actual reason found and rest of Pega0005 alerts were getting printed because of consequences since there were lot of cache misses which caused the rules/data to get picked from database not from the cache. 


Run static assembler and refer to the PDN article 

Published January 24, 2017 - Updated October 8, 2020

Was this useful?

100% 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