Issue  

After updating to Pega Infinity™ '25, scheduled reports are no longer executing as expected.  

Symptoms  

Scheduled reports fail to run after Pega Platform is updated to Infinity ‘25. 

Error in logs

com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Job Scheduler [pyUpdateScheduledReportsWithCurrentTimezone] activity [pyUpdateScheduledReportsWithCurrentTimezone] execution marked as failed with message [Missing stream key property pyStreamName].

Steps to reproduce

Pre-update: 

1. Schedule reports. 

Post-update to Pega Platform 25.1: 

1. Run scheduled reports. 

2. Reports are no longer processed correctly, and tasks are removed from the queue.  

3. Existing recurring reports are incorrectly marked as 'Completed' rather than 'Scheduled'. 

Root Cause   

Job scheduler pyUpdateScheduledReportsWithCurrentTimezone was implemented in Pega Infinity '25 to handle daylight saving time adjustments. As a result of a defect, newly created reports are not scheduled accurately. The job scheduler cleans up and recreates scheduled entries, converting times to GMT instead of maintaining local time zone (eg CET). 

This is a product limitation which requires a local change. 

 Solution  

To avoid the Issue, use the below local change: 

1. Disable the pyUpdateScheduledReportsWithCurrentTimezone job scheduler:

• Navigate to the job scheduler configuration in your Pega environment. 
• Locate job scheduler pyUpdateScheduledReportsWithCurrentTimezone. 
• Disable scheduler pyUpdateScheduledReportsWithCurrentTimezone to prevent it from executing and causing the error. 

2. Manually execute the pyUpdateScheduledReportsWithCurrentTimezone activity:

If users run the pyUpdateScheduledReportsWithCurrentTimezone activity from one application, then the access group used is the one from the current application and it will schedule all the reports without application context.  If the shortcut used is from another application, the access group and the current ruleset list is not available in the current application and it will cause the issue   

This manual retrigger needs to be done by a specific operator, and they may either have access only to a single application or multiple applications.

 If the operator has single access groups/applications: 

• Run the pyUpdateScheduledReportsWithCurrentTimezone activity manually to re-trigger the scheduled reports. 

 If the operator has multiple access groups/applications: 

Either:

• Create a dedicated operator with only one access group and run the activity per application. Perform the same for all applications.   

Or:

• Save As the Job Scheduler into each application’s ruleset and change the context to Specify access group and provide respective access group so that each app has its own job scheduler. Perform the same for each application/access group. 

References

Withdrawn and deprecated features 

Withdrawn support for user-defined functions in staging and production environments