Problem scenario

We have identified an issue with Agent Processing when attempting a restart, in the following scenario:

• Where an agent process is scheduled to run daily, or every weekday, at a specified time
• It runs on one node type
• This is isolated to environments where the system level time zone of the server differs to the user defined time zone being used for the agent runtime.  This will affect Kubernetes environments using our docker images, for running the Pega Platform, where the system time zone is set to UTC.

When rescheduled the agent may run on the day after the restart, skipping the current day’s run.

Hotfixes

We are providing critical hotfixes for the following affected versions of Pega Platform:

This issue doesn’t affect Job Schedulers which are a replacement process for Agents. Pega recommends clients utilize Job Schedulers in place of Agents. For example, If you have custom Agents affected by this issue, you can also simply remove/disable the agent definition and define a Job Scheduler to run the same process.

For more information about Job Schedulers check out: Managing job schedulers