Skip to content

Continuously Running Jobs

Joseph Huckaby edited this page Jun 30, 2019 · 3 revisions

Sometimes you need a job to run continuously forever. Meaning, even if a job exits, you want it to restart and keep running no matter what. Cronicle now supports this by using On Demand timing and the Chain Reaction system.

Here is how to set up a continuously running job. First, edit your event (the event must be previously saved) and set the Timing to On Demand:

On Demand Timing

Then, open the Chain Reaction system and link up the event to run itself on completion. Meaning, select the same event to chain that you are currently editing. You can choose to do this for successful exits only, or also for errors:

Chain Reaction Setup

Then click "Save Changes" at the bottom of the page. You'll have to start the job once manually by clicking "Run Now".

The event will now continuously spawn a job each time it exits.

Make sure to set your event's Timeout accordingly, and do not set any Retries.

Note that if you want to stop a continuously running job, you can simply abort it by clicking the "Abort" link on the Home tab. As of Cronicle v0.8.30, manually aborted jobs will not fire off a chain reaction, even if you have an event listed to run on failure.

Thanks to user @Jacketbg for coming up with this technique!

Clone this wiki locally