This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
The following error message is seen in the K2 host server log:
"Error","General","1","GeneralErrorMessage","K2Worker.ExecEventEscalation","1 Process instance is in an error state at K2Worker.ExecEventEscalation(K2AsyncItem )"
Based on the reported error message it is possible to see that it is an escalation event which is failing as well as the time stamp of the failure.
Please check the [Server].[Async] table to find the record related to the failed escalation which will give you the ProcInstID. With the ProcInstID you can find the process name as well as an entry in Error Profiles for the specific process instance. In Error Profiles you may see that the error date is preceding to the escalation error date. That means that when the escalation event fired, the process instance had already been in an error state, hence escalation failed too.
You can search/filter Error Profiles by ProcInstID. If the instance cannot be found there you can use the Process Instance SmartObject (Workflow Reports > Workflow General > Process Instance) to get a list of Process Instances and filter it by ProcInstID. This SmartObject allows you to find the ProcessSetID which you can use to get the process name by using: Process Overview SmartObject (Workflow Reports > Workflow General > Process Overview).
You need to address the specific error message that you see in Error Profiles for the process instance to prevent escalations failures in the future.