I had a problem for the last two years when the time changed due to daylight savings time. For the entire day, all my agents run one hour later than they are scheduled to run. For instance, an agent scheduled to run at 10:00 runs at 11:00 AM. When I do a “Tell Amgr Sched” at the console, they show as being scheduled to run at 11:00 AM and not the 10:00 AM that is listed in the agent’s properties. Any agents scheduled to run at 11:00 PM or later just don’t run that day.
I contacted Lotus Support and they tell me that Notes is working as designed. What?!?! This presented some problems for us that could potentially have had a $value impact to us. We have several agents that supply data to other systems that run other processes and jobs on schedule. Without the data from Notes, or with the data late, these processes fail and report incorrect information.
OK, so it’s only one day a year, but come on! One day a year we have to find each agent that runs that day and set it to run an hour early, so it will run at the right time?!?! Yes, says Lotus. That’s what we have to do. And they recommend not scheduling an agent after 11:00 PM since it will not run at all. Oh, great! Is that documented anywhere? Then of course, we have to set them all back to the correct time the following day. That is ridiculous! Does anyone else feel the same way or am I over-reacting? I see this as a pretty big bug, (even if it is only one day per year) but apparently it’s just a feature!
Subject: Daylight Savings and Agent Schedules - Are You Kidding Me?!
I don’t think you’re over-reacting. I agree. Although it doesn’t surprise me.
Subject: Daylight Savings and Agent Schedules - Are You Kidding Me?!
So don’t set your server to switch to DST. DST is nothing but confusing anyway.
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
Hey dude! You check your email or what? 
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
I sent a reply! Thought you were ignoring me!
Will send it again. 
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
Maybe Yahoo thinks it’s spam. Try sending here: willy_lorenzo@kmssolutions.com
Subject: Daylight Savings and Agent Schedules - Are You Kidding Me?!
Hi Karen, I am a little scared replying to your post because I know this is not the answer you want to hear… but let me see if I can explain better why this is working as expected.
Agent schedule is based on interval between agent runs. So a daily agent will run 24 hours after the time it ran last, and an hour agent will run one hour after it run. The server runs agents on behalf of many people, and given that there is a limited number of executives this is the “fair” algorithm, otherwise some long running agent schedule frequently would take over the server creating a denial of service for other agents.
The way scheduling works is documented in the help, although the relationship to DST is not called out explicitly.
Here is an excerpt from help text from the topic “triggering an agent on a schedule”.
“Note that agents are scheduled according to the interval you set up, not the exact time of day. For example, if you schedule an agent to run hourly, it runs about one hour after the last time it ran.”
Hope this helps!
Ducking out of the forum… Julie
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
This brings up a few other questions.
Why doesn’t it run an hour late from that point forward then? Since it runs at 11:00, rather than 10:00 on the day of the time change, the following day it should run 24 hours later as well, which would put it at 11:00 again. It must be adjusted somewhere and if so, why can’t that adjustment happen on the day the time changes, instead of the following day?
Also, what if I have an agent that for whatever reason - busy server, scheduling conflict, etc - runs 15 minutes late. Does that mean that the agent will forever run 15 minutes late? There must be a way to reset it? Does re-saving the agent have an affect? Or would I have to create a new agent and copy and paste my code in?
Thanks for any further info you can provide.
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
For effeciency the next run time in stored in the agent at the time it finishes running (that’s why it is able to adjust after it ran but not before). The algorithm tries to minimize the schedule “creep” as much as possible.
Subject: RE: Daylight Savings and Agent Schedules - Are You Kidding Me?!
OK. I can understand what you’re saying. But I still think it’s a major problem. I was under the impression that the agent cache reset itself every day at midnight and assumed it would reset an 11:00 AM agent to run at 11:00 AM. I didn’t realize it would run 24 hrs after it ran last. Thanks for responding. At least I have a better answer for my manager, if not a solution.
Subject: Daylight Savings and Agent Schedules - Are You Kidding Me?!
I had this happen to me also on Sunday. Friend of mine and I thought we were going crazy. Even rebooted my server to see if that would correct it. Didn’t help.
Thank you for posting this, Karen.