Interesting technote on maximum execution time of LotusScript agents

I was quite surprised the read the snippet from the cited technote below but after thinking about it, it makes sense. How would the AMgr know beforehand how long time the agent would run and hence how to keep the Terminate event inside the maximum execution time…

“By design, the Terminate event will execute after an agent has been halted for passing the time-out setting. The best coding practice would be to have only necessary clean-up operations within the Termination event. The main operations of the agent should reside in the Initialize event.”

Via the Lotus Support RSS feed: Terminate Event of a LotusScript Agent continues running after the Max Execution time (technote 1201324)

Published by

lekkim

Positive, competent, out-spoken, frank and customer focused architect and developer with a strong foundation in web, cloud and product development. I'm a strong advocate for API first and cloud based solutions and development. I have a knack for being able to communicate and present technically complicated matters in conference, customer and training settings. I've previously acted as team member and leader in a product organisation.

One thought on “Interesting technote on maximum execution time of LotusScript agents”

  1. Interesting. This would be one way to make your scheduled agent that “must run” work without having to persuade the admin guy to reconfigure the server document. Not best practice I know …

Comments are closed.