Hi all, is there a way to skip an node when error happens? I mean when

eaglez over 11 years ago

Hi all,
is there a way to skip an node when error happens?
I mean when it is hung in red status?
I know i can add an exception flow to deal with green status.

I'm calling a web service which returns a xml and i use it to create a document.
before the web service, there is a task which is used to create the request soap.
and after the web service , the smart service "Appian Document from base64" will create a document.
an unexpected error could happen in all of these nodes,
and result in the process being stopped.

in this case, exception flow doesn't work and the node can not skipped.

Can someone help me, please?

Thank you very much...

Discussion posts and replies are publicly visible

Top Replies

Sathya Srinivasan over 11 years ago +1
Appian Employee

Ideally, if a node fails, then there is a reason behind it that requires fixing. For e.x. if the WS fails, then you need to rectify the service before the processes down the flow can execute. There is…

Parents

0 Sathya Srinivasan
Appian Employee
over 11 years ago

Ideally, if a node fails, then there is a reason behind it that requires fixing. For e.x. if the WS fails, then you need to rectify the service before the processes down the flow can execute. There is a good chance you may have a step down the flow that depends on this data. If you skip this step (let's say) then you may end up passing bad data throughout the flow.

Now, in terms of solution, I have heard some discussions of using a timer (in parallel) and if the service executes successfully, it terminates the timer, if not, then the timer will move forward with some 'indicator' to say that the node had failed. I personally don't think this is a good design and have never used such an approach.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Sathya Srinivasan
Appian Employee
over 11 years ago

Ideally, if a node fails, then there is a reason behind it that requires fixing. For e.x. if the WS fails, then you need to rectify the service before the processes down the flow can execute. There is a good chance you may have a step down the flow that depends on this data. If you skip this step (let's say) then you may end up passing bad data throughout the flow.

Now, in terms of solution, I have heard some discussions of using a timer (in parallel) and if the service executes successfully, it terminates the timer, if not, then the timer will move forward with some 'indicator' to say that the node had failed. I personally don't think this is a good design and have never used such an approach.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data