Notifications

46 views

Symptoms


After Kingston upgrade, on closing CTASK, change is not closing and issue occurs only in prod instance

Release


KP 6

Cause


The issue happened due to extended database lock time. 

Resolution


The active and close variables are related to a "Set Values" activity. 

Looking at the node logs, There is a lock time in the database.

Due to this lock-out time, the active and close variables were not updated and therefore the change request remained open.


 To resolve the issue, an index was created on the task table and it resolved the issue. 

 

Article Information

Last Updated:2018-08-15 10:28:04
Published:2018-08-15