Hi,

I have a process workflow where an exception might occur within one Action. I need to react on this exception in the workflow. That means I don’t want to skip the entire processing

I just want to react properly by setting an error variable and skip this specific item (my process iterates over a list of items).

Now I tried to model my Action together with a Fault Node within a CompositeNode as seen in the User manual section on exception handling. The outgoing connection

of my Action is connected with the Fault. The outgoing connection of the CompositeNode is connected with the next Action. When I run the process it comes to the Action node and hangs there if no exception occurs (the next Action is never reached). Looking at the model this is reasonable since the outgoing connection leads to the Fault node. So my question is how can I properly model this kind of exception handling, where I need two ways of execution (one if everything goes fine, and one for fault handling)? Wrapping everything inside a CompositeNode alone does not seem to be sufficient…

Thanks in advance for any help!

-Jan