Support Article
pyRuleExecutionMessagesLogged does not return current logs
SA-14130
Summary
The pyRuleExecutionMessagesLogged activity is not returning results for today. The latest results are always from yesterday.
Error Messages
Not Applicable.
Steps to Reproduce
- Create a new user and access group.
- Set Rule Security Mode to WARN on access group record.
- Login as new user and create a new work object.
- 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.
Resolution
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.
Published September 23, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.