Thanks Mahesh, that’s some useful information. The only question that I have left is, when debugging through such flow service with transient error setup - when IS retries for ISRuntimeException as thrown thru pub.flow:throwExceptionForRetry - does debugger haults on breakpoints? If not how do we determine whether the IS is really retrying?
I tried using the getRetryCount flow service in the block where I am later executing the flow:throwExceptionForRetry service but I can’t capture the count for retry. I am attaching the snippet/ screenshot of the flow service that I built to test this process out. I was generating error by changing the password of server alias it uses to connect. But still same behaviour.
Let me know.
Here you go!, refer chapter 41 Building Services that Retry from 9-12_Service_Development_Help.pdf