We have a .NET Service that creates 100 - 1000 workflows each morning. The .NET Service uses the K2 cluster name to create the workflows which routes to 1 of the 2 K2 servers we have. It can process about 150 workflow creations in 2 mins so they are created very quickly.

Once the workflows have been created an escalation fires on the 1st step after approx 2 seconds to perform some processing. The escalations sometimes run very slowly and this looks like it is due to all escalation firing on 1 x K2 server however on the mornings they run normally the escalation fire on both servers.

A few questions;

1) Has this issue been seen before?

2) How does K2 decide what server to execute an escalation?

3) How do we force K2 to escalate on both servers consistently to avoid any slow running escation processing?

Thanks.