Hi,
Is there any way to handle exception and continue process execution? In other words if error occurs i need to go to different route (route 2 on print screen). It is not possible to query db to check if error will occur or not.
Simplifies process model. In real case there are much more nodes after writing to db.
Discussion posts and replies are publicly visible
Hi Furman
Please see below one of the approach that I can suggest. You can add delay after start node. If Write to DB breaks, after some time timer will start and trigger the flow.
Thanks,Sandeep
Endorsed!
Hi Robert,
From the above conversation I could understand we can't proceed to an exception flow when the node is paused or broken due to a technical error, so in this case may I know in what scenarios we can use the exception path defined for a node (ideally a smart service or user input task or script task). Much appreciate if you can provide an use case please.
The term "exception" does not mean a technical exception, like in Java, in this case. This is about a functional or business exception which results in a different flow in process.
One common example of this - suppose you have a process that sends out a survey, where each user receives a task. However, the task deadline is 7 days after the survey is started. A good use for an exception is to trigger the exception after 7 days to skip the task if the user did not complete it. This will ensure the process does not wait indefinitely for the user to complete their task.