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

Agent skipped schedule on one day

SA-33382

Summary



We faced an issue where an agent skipped one day in its schedule after a restart.

This has happened on a couple of occasions, it appears to happen when the schedule is updated from machine in a different time zone close to midnight.

Error Messages



Not Applicable


Steps to Reproduce

  1. Require server and client to be in different timezones, for example: MST and EST.
  2. Create a weekly agent run time to run at 4:30am MST.
  3. At 11:30pm change the schedule or restart from the EST machine.
  4. Next run time misses one day.


Root Cause



There was a defect in the weekly pattern next run time calculation when crossing timezones.

Resolution



Apply HFix-31340.

Published February 22, 2017 - 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