AnsweredAssumed Answered

Problem with Timer events.

Question asked by shreekant on Jun 3, 2014
Latest reply on Oct 28, 2014 by martin.grofcik
I have been facing problems with timer boundary events as well as timer intermediate delays. Hence, I created a simple workflow to test things out and streamline the problem.

I have a subworkflow, which has a user task, and it has a timer boundary event, which leads to a user task.

When I start the workflow, the user task inside the workflow, and the escalation task both start at the same time, in spite of having 5 minutes on the timer event. When I look into the 'my instance', it says 'user task' was started moments ago, but finished 6 hours ago (because the escalation task cancels that one), and escalation task was started 6 hours ago.
There is some sort of time zone issue, because of which activiti engine thinks that the workflow was started 6 hours ago. I am not sure about this. But if this is the case, where can I configure the time zones? Any other ideas?

Thank you for your help!