< class="prominent-subhead ">

Known Issue: All Asynchronous functionality depends on time sync between the K2 Server and the SQL Server


When running K2 in a distributed environment, configure your K2 server and SQL server to use the same time zone and synchronize the time. If these two servers do not use the same time zone, asynchronous events are either delayed or do not start, such as with the following items: 

  • sub workflows
  • escalations
  • start rules
  • workflow rules
  • other asynchronous events 


There are no specific error messages for this issue, however, you may experience issues similar to the following behavior:

  • If your K2 server is configured for a time zone that is one hour ahead of the time zone of your SQL server, the IPCAsync entry to start a sub workflow waits one hour before starting the workflow. This is because the entry in SQL comes from the K2 server and does not expire until that time is reached on the SQL server. Once the workflow is complete, another IPCAsync entry is created to go back to the main workflow which also waits one hour before continuing with the main workflow. The mismatched time setting creates a two-hour delay.
  • If your SQL server is configured for a time zone that is one hour ahead of your K2 server, no asynchronous events start. This is because the SQL entries always appear in the past, an hour behind, so the server assumes the events have already happened.

This does not affect synchronous workflow events.


Set the K2 server and SQL server to the same time zone and synchronize their time values.

K2 recommends that you synchronize both computers to the same internet time source, such as time.windows.com or time.nist.gov.