Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Recurring agents run one hour behind/ahead due to Daylight Savings Time

Updated on September 10, 2021


For Process Commander versions prior to 5.4, recurring agents will run one hour ahead (or behind) after Daylight Savings Time starts or ends; a manual change must be made to the agent definition.






When defining a Recurring agent, you fill out the Start date and time in the Recurrence dialog box (reached by clicking the Advanced button in the Agent Schedule form).


The date/time you enter in the Start field is interpreted as the local time in the time zone of your local server, and is the desired time of the first execution of the agent.  Subsequent executions of the agent are 24 hours later (or multiples of 24 hours).

When Daylight Savings Time starts (or ends), the time between agent executions is one hour more (or less) than 24 hours, so the agent will begin executing at an incorrect time.



1.  Shut down the problem agent (using the System Management Application).

2.  Open your Agent Schedule instance and click on the Advanced tab to open the Recurrence dialog box.

3.  Change the Start field to reflect the current date, and the time that you wish the agent to run.  Click OK.

4.  Restart the agent through the SMA.


NOTE:  This change will have to be made at the beginning and at the end of Daylight Savings Time (twice a year).


This issue was resolved in Version 5.4, where agents automatically handle the Daylight Savings Time changes; recurring agents which are scheduled to run at the same time each day will continue to run at that time, even after a time change.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us