TROUBLESHOOTING
1. Insufficient access in the database ACL can prevent an agent from running properly. For example, a user may design an agent that copies selected documents from database A to database B. If the user -- and by extension, the agent -- doesn't have Author access in the ACL of database B, the agent runs, but it is not allowed to copy the documents. To determine if this problem exists, examine the Agent Log for access errors after the agent runs unsuccessfully.
2. If an agent won't run on a particular server, check the Agent Restrictions on the Security tab of the Server document. This section contains the "Run simple and formula agents," "Run restricted LotusScript/Java agents," and "Run unrestricted LotusScript/Java agents" fields that specify who has access to run agents on the server. Although a user who has the appropriate access in the database ACL may be able to create an agent on the server, without the appropriate access in the Server document, the user can't run the agent.
4. If a LotusScriptâ„¢ or Javaâ„¢ agent terminates before completing its tasks, check the "Max LotusScript/Java execution time" fields in the Server document. If a complex agent requires more time than is scheduled, the Agent Manager terminates the agent before completion.