Issues regarding strong versioning of K2 Workflow process


Badge +2

Hi,


 


I recently notice an issue with K2 where after the user approves (client event), the workflow is hit with a error/bug further down the process in other activities. So we quickly fixed the bug and redeployed the new Workflow process; we were expecting that by retrying from the error point, it will be able to continue the processing smoothly but it still hits the same error. Furthermore, other process instances also encounter the same error even though we though the bug is already fixed.


Finally we realize that the old process instances still reference the previous version and will not be able to execute the newly added code. So what are the recommended ways to overcome such issues? Do we have to retrigger the workflow with a new process instance?


 


Regards,


lyf


2 replies

Userlevel 4
Badge +14

If in understand correctly you have process instances in error state, due to a bug and you fixed the bug in the latest version of the process?  Now you need to get these error instances to run on the new fixed version.


In VS > View K2 Process Management. Here you can view the instances in Error state and retry them on the new version.


Refer to


http://help.k2.com/en/k2blackpearluserguide1230.aspx?page=Reference-ST-Error_Repair.html


or in K2 docs >  K2 Designers > K2 for Visual Studio > K2 Designer for Visual Studio > K2 Process Management Overview


HTH


Vernon

Badge +11

K2 processes are versioned.  Once an instance starts, it remains on that version  until it is complete.  You can use the error repair functionality or Live Instance Management API to apply a fix to running process instances.


If K2 automatically upgraded running processes to the latest version, the result would be complete chaos and unpredictability as the new version could be logically inconsistent with the old one.

Reply