pub.flow:throwExceptionForRetry

WmPublic. Throws an ISRuntimeException and instructs the Integration Server to re-execute a service using the original service input.

wrappedException	Object Optional. Any exception that you want to include as part of this ISRuntimeException. This might be the exception that causes the pub.flow:throwExceptionForRetry service to execute. For example, if the service attempts to connect to a database and the connection attempt fails, you might map the exception generated by the database connection failure to the wrappedException parameter.
message	String Optional. A message to be logged as part of this exception.

Use the pub.flow:throwExceptionForRetry service to handle transient errors that might occur during service execution. A transient error is an error that arises from a condition that might be resolved quickly, such as the unavailability of a resource due to network issues or failure to connect to a database. The service might execute successfully if the Integration Server waits and then retries the service. If a transient error occurs, the service can catch this error and invoke pub.flow:throwExceptionForRetry to instruct the Integration Server to retry the service.

The pub.flow:throwExceptionForRetry service should be used for transient errors only.

Only top-level services or trigger services can be retried. That is, a service can be retried only when it is invoked directly by a client request or by a trigger. The service cannot be retried when it is invoked by another service (that is, when it is a nested service).

You can invoke the pub.flow:getRetryCount service to retrieve the current retry count and the maximum specified retry attempts for a service.

If the trigger service is written in Java, the service can use ISRuntimeException() to throw an exception and retry the service. For more information about constructing ISRuntimeExceptions in Java services, see the webMethods Integration Server Java API Reference for the com.wm.app.b2b.server.ISRuntimeException class.