the message is still being suspened. Anyone familiar with this?
I call a webservice from an orchestration in a long-running scope with an exception handler of type “System.Web.Services.Protocols.SoapException”
I’m logging everything so I can see that the exception handler catches the exception but it still insists to create a suspended instance with:
“WebException: Unable to connect to the remote server
SocketException: No connection could be made because the target machine actively refused it”
I’d gladly appreciate some help. Retry count of the send port is set to 0