@Shreyoshi_Das , Sometimes there will be delay in triggering timer events and depends on the number of jobs being executed in engine at that time. For more details refer this post:
Hi Atul
I would also mention that timers are best interpreted as ‘will fire after the expiration time’. Hence as far as BPMN is concerned, the meaning should be interpreted as ‘will not happen before…’ as opposed to ‘will happen at…’
As pointed out though, there are system parameters and behaviours which can influence the actual timer latency…
regards
Rob
Hi,
Id like to point out that the intent of a timer is the transition is guaranteed not to occur before the time is up. The transition can occur sometime after the time is up…
The reason you may see a 50s delay is because, the time may be up and thus the transition as a job in the job table becomes available for job acquisition. However if the job acquisition thread is sleeping, the job will wait until the thread wakes up. Hence the job acquisition thread pools the job table.
You can configur…