Re-enqueue immediately on missed job

[maltoe]

It would be nice if the reschedule method could detect if a job had passed the next schedule time while running, and would re-enqueue it immediately instead of waiting for the next schedule time.

Better example:

• We have a service that runs hourly to retrieve some updated data from an external API.
• Usually it has a runtime of well under an hour and everything is fine.
• Sometimes though, it might run for, let's say 1h10m, and thus miss the "next" schedule time.
• Current behaviour is to schedule it for in 50mins then, but I'd like it to (optionally) reschedule immediately, so it can start processing the next batch of data right away.

What do you think?

[dsander]

I think that makes sense for certain jobs. The behavior should be optional because there are also situations in which one wants to make sure the job only runs at the configures times and not, for example, twice per hour.