We have configured timer event to trigger after 20S. but we observed that it gets triggered after 22 or 24 S. Is this expected behavior or is there any bug?
Timer event >> Timer definition>> defines time after which that event will be triggered (Not the time when exactly it should be triggered) . As this is wait state it actually creates job and pick that job after that specified time. If we configure 20S then We noticed that our event is getting completed after 22S or 24S etc.
This can be expected behavior. The accuracy of the timer event relies on how frequently the job executor looks for jobs.
Once the timer is expired the job becomes available to be picked up by the engine and depending how often the job executor looks for new jobs there could be a descrepency of time between when the time expires and when the job actually gets picked up.
You can increase the frequency at which jobs are acquired by changing the job executor settings.
Thanks for the response 