Admins are often cast in the role of deploying and managing agents. In fact it's the best practice, ask Paul and Bill. The Designer client has gotten very fat, and Eclipse takes quite a while to load it. For an admin to enable/disable/schedule an agent, she needs to launch the ...
LotusScript agents that run longer than the limit which is configured in the server document are automatically terminated by the Agent Manager. There is currently no way to handle this exception programmatically and execute a graceful termination / rollback and thus maintain data integrity.
I suggest one solution may ...
1. Agent Manager console command "pause". Could be useful in debugging.
2. (maybe) Add server document parameter on the Agent Manager Tab, "Pause between" which could be used to specify time ranges when the agent manager holds state / hibernates. This could be useful for allowing things like backup ...
Add a field to the server document that the agent manager would check so that it would only process agents from specfied databases or paths eg live/customers/acme/*