Issue  

After upgrading 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: 

Disable the 'pyUpdateScheduledReportsWithCurrentTimezone' job scheduler: 

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

Manually execute the 'pyUpdateScheduledReportsWithCurrentTimezone' activity: 

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

References

Withdrawn and deprecated features 

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