Remedy Adapter throws the following exception classes that you should be aware of as you build integrations using the adapter:

In all cases, the adapter passes the underlying exception to the adapter runtime, which wraps it in a container exception that it then passes to Integration Server. Integration Server then serializes the exception and returns it to the client service. Typically, that client (for example, a flow or Java service that calls an adapter service) will include logic that traps these exceptions and branches accordingly. For information about how to trap the exception in a flow, see the webMethods Service Development Help for your release.