Scheduled Task Event fires every 3 minutes
After upgrading from Pega 7.1.7 to Pega 7.1.8, performance declines with higher CPU ulitization than the previous release, due to one Scheduled Task Event that fires every 3 minutes, and generates an exception on every attempt.
Exception is observed in the XML of the scheduled task work object for each attempt made to process the case.
The reference (unspecified) is not valid. Reason: property name contains invalid character at position 3
Steps to Reproduce
1. Upgrade from Pega 7.1.7 to Pega 7.1.8.
2. Run the scheduled report configured to build regularly on a scheduled time of the day.
The root cause of this problem is a defect in Pegasystems’ code/rules. A scheduled report is configured and working at the scheduled time per day. After upgrading to Pega 7.1.8, attempts to send out one or more reports continue every three minutes, even though the scheduled time only shows one time per day (in this case). The Scheduling Agent stops reviewing the current schedule and repeats the report every time the agent wakes up to check for more reports.
This issue is resolved by HFix-22558 which ensures that the max retry count does not get reset and the report execution stops when it should and only fires on the scheduled date or time indicated.
0% found this useful