You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jobs are executed in parallel in case the job runs longer than the scheduling interval even if configured with withConcurrency(1) and withMaxRunning(1). A minimal sample can be found here: https://github.com/hammer90/momo-scheduling
steps to reproduce:
define a job to run every ten seconds
let the job sleep for 30 seconds
expected result:
job is always executed only once
actual result:
after the first execution of the job the job is executed in parallel
with the timing from above constantly three times in parallel
Thanks for reporting this. @YaniKolev was able to reproduce this.
We found the bug already, the problem is that the internal ping accidentally overwrites the information on how often the job is already running. Working on a fix.
Hello,
jobs are executed in parallel in case the job runs longer than the scheduling interval even if configured with
withConcurrency(1)
andwithMaxRunning(1)
. A minimal sample can be found here: https://github.com/hammer90/momo-schedulingsteps to reproduce:
expected result:
actual result:
Some logs from the sample repo:
best regards
Sebastian
The text was updated successfully, but these errors were encountered: