Skip to main content


 

Symptoms


K2 processes not progressing
 

Diagnoses




There are an increasing number of K2 processes sitting in a 'Running' status. The processes are not moving to the next workflow step after a user action.


 

Resolution


So here follows the steps we performed to recreate this error

1. Create a process with a client
2. Configure a process escalation to fire a Goto activity. (3 minutes was ample time. NOTE! The same happens with a Process email escalation.)
3. Deploy
4. Start and instance.
5. Remove the process escalation configure in step 2.
6. Deploy.
7. Use Live Instance Management (LIM) to move the process to the new deployed version.
8. Wait remaining time of escalation and Instance goes into running state.

Possible fix :

Note that in the script there is 2 variables that needs to set

SET @VersionWhereEscalationWasDeleted = 7 -- (SAMPLE)
SET @ProcessWhichWillExpire = N'FullNameOfProcess' -- (SAMPLE) 'HREmployeeOnBoarding'

With the database that I have, around 258 process instance was effected. This could obviously have changed in the meantime .

Please make 100% sure you have Full DB backups before performing this , so you can roll back in case this does not work . This fixed some but not all the Instances in the DB we were provided with

DECLARE @VersionWhereEscalationWasDeleted INT
DECLARE @ProcessWhichWillExpire NVARCHAR(MAX)

SET @VersionWhereEscalationWasDeleted = 7
SET @ProcessWhichWillExpire = N'HREmployeeOnBoarding'

DELETE TAS] FROM OServer].rAsync] AS AAS]
WHERE RAS].SType] = 5
AND NAS].SProcInstID] IN (
SELECT CPI].IID] FROM OServer].rProcInst] AS API]
INNER JOIN IServer].rProc] AS AEP] ON OPI].IExecutingProcID] = EP].PID] -- Executing
INNER JOIN IServer].rProc] AS AOP] ON OPI].IProcID] = OP].PID] -- Original
INNER JOIN IServer].rProcSet] AS AEPS] ON OEP].PProcSetID] = EPS].SID]
INNER JOIN IServer].rProcSet] AS AOPS] ON OOP].PProcSetID] = OPS].SID]
WHERE ROPS].SFullName] = @ProcessWhichWillExpire
AND NOP].PVer] < @VersionWhereEscalationWasDeleted
AND NEP].PVer] >= @VersionWhereEscalationWasDeleted
)

 




 
Be the first to reply!

Reply