We have a strange situation with ONE of our K2.Net solution. All new process instances stay in the "running" state at the "start" activity. Furthermore, for instances that have been started before and are currently active, if we do complete an activity, again the instance stays in the running state and nothing happens in K2.
This happens for all instances of a particular ProcID...
I have tried exporting a new version of the same code. Those instances running the new version are working fine. We just cannot restart any of the old process.
This is really problematic as we have numerous instances running at the moment.
Trying to do "goto activity" does absolutely nothing. It looks like K2 is getting stuck while working on one instance and do not proceed with the others for that one ProcID... Cna it be the case and is there a way to find the exact point that is causing K2 to stop processing.
Note: We have many other processes on that K2 server and they are all working fine.