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

LastRun for scheduled tasks has a delay



The LastRun value for scheduled tasks has a delay of three minutes.

For example, if a report is scheduled at 3 AM, the mail is delayed by 3 minutes.

In the Reporting:Components landing page, the LastRun value displays as 3:03 AM. However, the NextScheduledRunTime value is updated correctly.

Error Messages

Not Applicable

Steps to Reproduce

  1. Open the report browser.
  2. Schedule a task.

Root Cause

This behavior is as per  Pega product design.


Here’s the explanation for the reported behavior:

The LastRun time value depends on the processing time and the number of queue items. The delay for the LastRun time value is an expected behavior according to Pega Product functionality.

The notifications are missed due to the number of waiting queue items which is updated twice before processing.

According to the functionality, the system takes the current updated time of the scheduled task during the processing time and receives the notification as per the configuration.

Published August 19, 2019 - 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