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 Performing Guardrail Report



User noticed PEGA0005 ( Database query time exceeds limits) alerts related to an OOTB Report Definition - Data-Rule-Summary pzWarningsIntroduced.

This report definition gets executed mainly in the Developer Portal (for displaying rule level warnings) and can have an impact on the system performance as they on-board more and more developers and developer activity increases.

They also see huge number of PEGA0001 (Browser interaction exceeds limit) alerts which could be a direct consequence of these PEGA0005 alerts.

Error Messages


Steps to Reproduce


Root Cause

There is an outstanding performance issue with the guardrail SQL that is executed, which causes long running queries and timeouts.


Add the useLayerCakeSchemaChanges parameter to the prconfig.xml file and set it to true, this was added in ML6 and causes the SQL to executed in a more efficient manner.


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