This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
When a K2 workflow has a loop back line rule, the process instance stays in a waiting state. Using the SourceCode.Workflow.Client API to open the process instance to retrieve a data field value, and then using the Serial Number to finish the Async Server event in the workflow results in deadlock errors.
Deadlock errors are visible in the HostServer.log file.
- Ensure you have K2 4.7 installed.
- Download and install the K2 4.7 August 2017 Cumulative Update from K2 Partner and Customer Portal.
- Get the K2 4.7 August 2017 Cumulative Update FP10 from Regional Support.
- Install the K2 4.7 August 2017 Cumulative Update FP10 to apply the fix.