First Boundary event fires near 10 Seconds after it's due date after that execution happens at exact time.

piyush_kaizen — Mon, 17 Apr 2017 10:24:11 GMT

I am testing Activiti boundary event with repetition.REPEAT_ = R20/2017-04-17T15:46:17/PT30SDUEDATE_ = 2017-04-17 15:46:47.000butExecuted at Mon Apr 17 15:46:57after that all execution happen after 30 SecExecuted at Mon Apr 17 15:47:26Executed at Mon Apr 17 15:47:56 Is it job executor precision issu

Re: First Boundary event fires near 10 Seconds after it's due date after that execution happens at exact time.

gdharley — Mon, 17 Apr 2017 15:43:53 GMT

Yes, it is a Job executor precision issue.

The default wait time for timer job execution is 10 seconds and it is set with this property in your configuration:

<property name="defaultTimerJobAcquireWaitTimeInMillis" value="1000" />

Just a note, in the Enterprise Edition, the timer wait time is set to 5 seconds.

You can update this by updating the engine.properties (if using an older version) or the Activiti Engine configuration class if using annotation based configuration.

Cheers,
Greg

‌

topic First Boundary event fires near 10 Seconds after it's due date after that execution happens at exact time. in Alfresco Forum

First Boundary event fires near 10 Seconds after it's due date after that execution happens at exact time.

Re: First Boundary event fires near 10 Seconds after it's due date after that execution happens at exact time.