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

pyRuleExecutionMessagesLogged does not return current logs



The pyRuleExecutionMessagesLogged activity is not returning results for today.  The latest results are always from yesterday. 

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create a new user and access group.
  2. Set Rule Security Mode to WARN on access group record.
  3. Login as new user and create a new work object.
  4. Run the pyRuleExecutionMessagesLogged activity again and look for warnings.

Root Cause

A defect in Pegasystems’ code or rules causes this issue. The pyRuleExecutionMessagesLogged activity only scans logfiles that specifically have the string "log" in the name. When using a dailyRollingFileAppender, the current day's logfile does NOT have "log" in the name (in the typical confirguration). This is only added once the file is rolled.


Perform the following local-change:

Modify the pyRuleExecutionMessagesLogged activity to find logfiles of your particular naming convention.
Alternatively, update the prlogging.xml file to fit the name search performed by the pyRuleExecutionMessagesLogged activity. 


Suggest Edit

Published September 23, 2015 - 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