Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
5808 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Call Webservice node errored out and process is active
vbhardwaj
Certified Senior Developer
over 7 years ago
Am calling SOAP Webservice from Appian process using Call WebService node. If the webservice is down or in case of any network connectivity issue, the call webservice node hangs with Error and process is stuck. Have tried to handle this using escalation. But escalation also does not work in this case.
Any idea how to handle this error ?
OriginalPostID-257248
Discussion posts and replies are publicly visible
0
rodgraham
Certified Lead Developer
over 7 years ago
Have you tried using an exception on the node? You could do a timer exception after certain length of time to follow an exception path
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
kondetiv
over 7 years ago
@vikrantb could you please comment the alert message here such that we can analyze the whats the issue exactly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vbhardwaj
Certified Senior Developer
over 7 years ago
@rodgraham - Have tried using exception on the node with timer but it didnot work as expected.
a) Service gets timed out in 2 mins, tried timer of 1 min on exception flow, it worked.
b) Tried timer of 3 seconds in exception flow, but it did not worked as Call Webservice node was errored by timeout after 2 seconds
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sparshs
over 7 years ago
@vikrantb: i will suggest you to add a boolean variable in the out put of webservice node and set it true once the webservice is executed successfully, You should also branch out another parallel flow from start node to a script node and on that script use a timer event to wait for 1min , if the boolean which you are using in output of webservice is changed to true or not , if not then put your flow to a user input task , where you can show user a message about the webservice not working.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ChristineH
Certified Lead Developer
over 7 years ago
The way I have handled this in the past is to handle it on the subprocess node in the model above this. Not sure if that will achieve your goal, but worth a chance.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
raghunandanj3904
Certified Senior Developer
over 7 years ago
If there is any data dependency on this WS execution then you are stuck and you need to manually restart this. No other option. Else, as chirstineh suggested, have a timer on the sub process call for 2 mins and if you don't get any response,retry (if required or move on).
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
chrism967
over 7 years ago
Where we experience issues such as this (usually on SSRS calls) we have a Boolean output of the WS call on success and a script task immediately before which restarts every 5 minutes for either 3 goes or until Boolean marks as successfully called.
Similar issues with Sharepoint integrations too.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
paule
over 7 years ago
I would agree with sparshs - branch from the start node with a timer where you perform some notification action - to the user and / or your support team if the timer expires and the web service has not completed (as indicated by the boolean).
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vbhardwaj
Certified Senior Developer
over 7 years ago
Thanks all for your comments.
As suggested am using timer in parallel flow with WebService call and checking whether the service got executed successfully.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel