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

Exception at <Node ID> GMT: Invalid delay time

SA-38577

Summary



User had scheduled the agent to run at 12.00 EDT daily in the environment. However, the agent did not run at the scheduled time.


Error Messages



Exception at <Node ID> GMT: Invalid delay time: < >



Steps to Reproduce



1. Create an agent to run at the scheduled time (12:00 EDT).
2. Observe that the agent does not run at the scheduled time.


Root Cause



In the case of an Agent scheduled to run "Daily" and at exactly midnight (12:00), the agent ends up being scheduled to run even a second prior to that, it would be the previous day in regards to the agent timezone that results in negative value in time calculation (Next Execution Time - Current Time)- it will interfere with the algorithm used to schedule the next run.

Resolution



Perform the following local-change:

Set the value of the agent to run few minutes after midnight, five minutes past 12:00 say 12:05 midnight.


Published July 5, 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