RE: Scheduled Agent Timeout Joseph P Gwizdaloski 3.Jun.06 04:02 PM a Web browser Domino Server 6.5.5Windows 2003
I fully agree that there is a development task to do here. This has already been addressed. The original question's focus was on why the Server did not time the agent out after the Max LotusScript Execution Time was hit.
An earlier post talks to the possible uniterruptability while executing a long running task, which may be the key as to why the agent was not terminated. If so, I am not sure what more my application can do. (Our developers have taken the right steps to test conditions and prevent looping in this case from happening again.)
If you have ideas on why the agent timeout failed, I would still be interested in hearing more on this point. Thanks.