Troubleshooting
Problem
The try/catch setup that's recommended for error handling works very well for standard WebMethods errors. With webService Connectors, though, user found it necessary to create a Branch step to check for and address SOAP-FAULT conditions.
User attempting to perform error handling entirely within a single flow service. They have labeled the try & catch blocks appropriately, and using the label addressing functionality inherent in EXIT to transfer control from the try block to the catch block. To explain the problem in detail have the following example.
Take two scenarios:
(scenario 1)
sequence - try
serviceA
sequence - catch
getLastError call
Where serviceA is just an EXIT $flow SIGNAL failure step.
(scenario 2)
sequence - try
exit - try - signal failure
sequence - catch
getLastError call
In the first scenario, getLastError returns a document with the appropriate pipeline and error information contained in it. In the second scenario, it does not. If signaling failure in both scenarios, shouldn't the getLastError command capture the appropriate error information both times? Please advise on this situation and the reason for this behavior.
Document Location
Worldwide
Log InLog in to view more of this document
Historical Number
Product Build 6.1, 6.5,7.1, 7.1.1
Was this topic helpful?
Document Information
Modified date:
20 March 2025
UID
ibm17218485