Execution interval of the service task

[rohwerj]

Also here is a link to a post explaining that behavior:

Job execution success > Job acquisition success (job lock exclusive?!)

found already an answer on this post by @thorben When a job executes and it creates new jobs that are immediately due, exclusive and in the same process instance, then the jobs are immediately locked and queued for execution by the current thread. That way they skip the acquisition cycle.