Troubleshooting agents

You can experience problems running agents at several points during agent development, deployment, and implementation. Try the following to help diagnose any problems.

  • Run the agent on the Notes® client.
  • Simulate an agent run (for all types of agents).

    Before running an agent on a live database, test it by simulating a run. The test also diagnoses whether the agent will run by checking security and schedule settings.

  • Review the Agent Log (for all types of agents).

    The Agent Log displays information about when the agent last ran and whether it ran successfully.

  • Use the Notes server console (for all types of agents).

    There are three server console commands available to display information about agent scheduling, status of agent queues and control parameters, and status of agent debugging settings that are in effect.

  • Set up the Agent Manager debug information (for all types of agents).

    You can specify that the Agent Manager record debug information about any combination of the following: control parameters, events, loading reports, memory warnings, performance statistics, execution reports, and scheduling. Messages appear on the server console and are recorded in LOG.NSF.

  • Run commands in the LotusScript® debugger (for foreground agents built with LotusScript.)

    Choose File - Tools - Debug LotusScript and run the agent. The LotusScript debugger appears and you can run any debugging command in the agent as you would for any LotusScript program.

  • Track information with the NotesLog classes (for background agents built with LotusScript or Java).

    The NotesLog class is added to your agent code and can capture information you want to track. The NotesLog class records the information in the Agent Log.

  • Check the Notes log database (LOG.NSF).