How to automate clearing or cancelling of the processes which stopped with errors?

Question

Hi, 
 Can someone help me in letting me know automating the processes clearance which has stopped with problems. The process which we have built are synchronized processes (short-lived), so there is no manual intervention of resuming the process if it stopped with errors. So in this case all the processes stopped with errors are still in the system and it is not cleared, the only way we found to clear the error processes is to manually cancel it or delete it. 
 Please suggest a way to Cancel a process automatically if the process stops with errors.

Regards, 
 Balaji.R

Robert Shankin · Answer

Hi rp_balaji 
 One way to handle this is to incorporate a timer in the process models where this condition applies. 
 In the example shown below, I just setup a 1 minute timer. This timer event node starts as soon as the process starts. One minute later it will end. For your requirement, this timer could last 1 hour, 2, hours, a day, or a week. It's whatever you need. 
 > This shows what the process looks like at the time of the error. 
 > After your prescribed timeout, the process terminates, even if there is an error .

Robert Shankin · Answer

Hi sahilb346 - 
 Please reconsider your suggestions here, in light of the following: 
 First, look at figure 1. I've extended the example process that I shared previously. This now includes a 1 minute exception timer in the task that fails. Simultaneously, I've changed the timer event in the timeout lane to 5 minutes. > figure 1 
 Next, look at figure 2. This shows the same process after 5 minutes. The write to data store task exception time never fired. This is because, the previous state of the task was "problem with task", and the timer never started. If the Timeout lane timer didn't exist, this process would live indefinitely until manually stopped. > figure 2 
 Now, look at figure 3 , and Consider unexpected outcomes. In this case, a task that is typically reliable, (the script task), fails. Without a dedicated timeout timer, set to fire based on a "safe" interval" your process will just "hang". >figure 3 
 Finally , consider whether or not addressing symptoms rather than causes effectively suits the business need. For example, is it really in the best interest of the product owner to systematically terminate error-prone processes? Or, would it be more beneficial to understand the root-cause of the errors and resolve that?

How to automate clearing or cancelling of the processes which stopped with errors?

Top Replies