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.
Event escalations from different workflows fire when they should not (for completed processes). The issue appeared after an upgrade of the K2 server.
In this scenario you may need to check the contents of the Server.Async table and test overall escalation processing using a test workflow. If nothing abnormal is found focus on the suggestion below.
In K2 server upgrade and migration scenarios you should also ensure that the K2 service is no longer running on an old server which may be kept in place during transition period for rollback purposes - make sure the service is not only stopped but also reconfigured as Disabled, to avoid its automatic startup on server start up or restart.
Make sure that the K2 service is stopped and disabled on your old server which has not been fully decommissioned.