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

pzWarningsIntroduced;doActivity Rule-Obj-Report-Definition



Exception in Pega log file.

Error Messages

"pzWarningsIntroduced*RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20141014T084715.995 GMT Step:" and pzWarningsIntroduced;doActivity Rule-Obj-Report-Definition;Java;RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20141014T084715.995 GMT Step

Steps to Reproduce

There is no specific use case to replicate this behavior.

Root Cause

Alert log file will have this entry if the query took longer than 500 ms to execute


Indexing option might improve the performance and eliminate this warning.PRConfig settings for Report Definition could be changed in the follwing ways:
prconfig setting Description default value PRPC Version
reporting/useStreamInJoinConditions to use unexposed property in Join conditions false 7.1.4
reporting/useLayerCakeSchemaChanges to use layer cake resolution approach and a couple of schema changes for performance improvement - pzClassType and pzRuleSetVersionMinorPatch true from 7.1.8
false in 7.1.6 and 7.1.7
database/useReportingDatabase to use an alternate database for reporting true pre-existing


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