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

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.

Error Messages

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.

Root Cause

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.

Published August 10, 2015 - 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