Overview of Throw Exception for Retry Failure

Throwing an exception when retry failure occurs allows the webMethods messaging trigger to continue with document processing when retry failure occurs for a trigger service. You can configure audit logging in such a way that you can use webMethods Monitor to submit the document at a later time (ideally, after the condition that caused the transient error has been remedied).

Step	Description
1	Integration Server makes the final retry attempt and the trigger service fails because of an ISRuntimeException.
2	Integration Server treats the last trigger service failure as a service exception.
3	Integration Server rejects the document. If the document is guaranteed, Integration Server returns an acknowledgement to the webMethods Broker. If a trigger service generates audit data on error and includes a copy of the input pipeline in the service log, you can use webMethods Monitor to re-invoke the trigger service manually at a later time. Note that when you use webMethods Monitor to process the document, it is processed out of order. That is, the document is not processed in the same order in which it was received (or published) because the document was acknowledged to its transport when the retry failure occurred.
4	Integration Server processes the next document in the webMethods messaging trigger queue.