Job Scheduler Starts again, but previous job not finished - any way to prevent?

CloverDX Platform
1

Hi,

We have a bunch of jobs scheduled to run on the hour. Occasionally it takes longer than an hour to finish the previous job (API data calls via a slow proxy server is the cause there). We don’t want the next job to start if the current job is running. Is there a way to configure the job scheduler to do this? If is sees a job with the same name running, don’t start it up again (only one job of that id running at one time)?

Thanks!

2

Hi,

You can set max_running_concurrently property on a job or a whole sandbox, by going into the CloverETL Server GUI, in the sandbox Config properties. If you set it to 1, only one job at a time can be executed. The other executions can be enqueued for later if you wish by setting the enqueuer_executions to “true”.

Also, you can try the HTTP API in a Jobflow to find out what graphs are running to ensure that you can run the following instance, you can read more here.