Yuri van Oers

A feature request, then. Worth adding, I think, though maybe tricky to do this consistently for all executors. @victorcoder WDYT?

Upon seeing my thoughts were: If it is known that a lot of jobs start at once and it is OK for them to not run exactly at the scheduled...

I see. I'm not a fan of using randomization to accomplish load spreading. While that would usually work fine, there still is a chance of it doing everything around the...

I came across an implementation that may be useful: The 'H' as used in Jenkins. See the H explanation in the [Cron article on Wikipedia](https://en.wikipedia.org/wiki/Cron). See its [referenced source](https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly) for...

@victorcoder What do you think? I'd love to build this but I'm only going to if this has a chance of getting merged.

Ideally the feature should go in robfig/cron, absolutely agree. But considering there's a bunch of PRs for adding non-standard cron features (some of which could also benefit Dkron) sitting there...

Interesting. An alternative could be to introduce multiple cron schedules for a single job. Not sure right now whether that would be easier or more difficult compared to "concurrency groups"....

> But consider this real-live example: ... How do you intend to prevent the value from being processed multiple times, sequentially? So, e.g. when the value has been downloaded and...

I suppose it would be easy enough to add a new API end point to clear counters, e.g. `DELETE /v1/jobs//counters`. Do you only want to do this via the API,...

Can you provide logs, the version of Dkron and how your platform is configured (docker, VMs, OS, etc)? Ideally I'd like to log in on your cluster and have a...