How to fix Lotus Notes Agent error “Unsupported trigger and search in the background or embedded agent”
Sometime I found this error raise when I run schedule agent by manual and I think this error is generated in a server-based agent (which can be a Web agent or any other agent invoked on the server) or embedded agent (an agent called by another agent) which references UI elements as trigger/search target settings in the agent builder.
For example, suppose you create an agent that has action menu selection as a trigger and all selected documents as a search target. When you invoke the agent from the browser, you receive the unsupported trigger… error.
The “all selected documents” concept is not understood within a Web agent; this setting is meaningful only in a Notes client. To fix the problem, change the target setting, for instance, to all documents or none. The following four options are not supported in this situation:
- All unread documents in view
- All documents in view
- All selected documents
- When documents are pasted documents
The obvious tip here is to always make sure that you set the trigger property of a WebQueryOpen or WebQuerySave agent to “Run once (@Commands may be used).” But it is also very important to be able to identify the errors that can be caused by the default trigger property so you can remedy them quickly. Below are ways to recognize this error both on the Web and in Notes.
Recognizing the error on the Web: When a WebQueryOpen or WebQuerySave agent does not run correctly, check the server log for an error message that says something like the following: “Unsupported trigger and search in the background or embedded agent.” If you get this error, you know you need to check the trigger property of the agent.
Recognizing the error in Notes: In Notes, the default trigger type can cause an error when you are writing an agent that is not designed to run on selected documents, such as an agent that searches documents in the back end and acts on
them. In this case, if you have not selected a document in a view, you will get an error message that says “Agent must be run from a view window.” If this happens, go back and change the trigger property of the agent to make it
function correctly.
Viewed 12604 times by 3825 viewers
