This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forย 
Search instead forย 
Did you mean:ย 

Schedule Task to run every 5 min

GBekkanti
New Contributor III

โ€Ž12-03-2018 04:10 AM

Hi Team,

I have a scheduled task for every 5 min. What happens if one execution is not completed with in 5 min. I have disabled the option โ€œDo not start a new execution if one is already activeโ€. Will it be in queue? or it will throw any exception. if it throws, what will happen to the previous execution? will it be stopped or executed completely?

For Example : I have scheduled at 5:00PM IST and the job is running still even after 5:16PM IST. what will happen to 5:05PM IST call? and 5:10PM IST call? what will happen to currently running job?

Thanks and Regards,
Gopi Bekkanti.

0 Kudos
3 REPLIES 3

tlikarish
Employee
Employee

โ€Ž12-03-2018 07:57 AM

The another execution of the pipeline will start. If there is a JCC that is able to execute it, then it will start executing.

The current job will run to completion.

Here is the documentation on scheduling a task for more basic information. Let me know if there are other gaps or questions I can answer.

GBekkanti
New Contributor III
In response to tlikarish

โ€Ž12-03-2018 09:12 PM

@tlikarish Thanks for your replyโ€ฆ

If we enable the option โ€œDo not start a new execution if one is already activeโ€, Can you please clarify me on what will happen for 5:05PM IST call? and 5:10PM IST call? what will happen to currently running job?

0 Kudos

RogerSramkoski
Employee
Employee

โ€Ž12-04-2018 05:10 AM

@GBekkanti If you check the option โ€œDo not start a new execution if one is already activeโ€ the current running scheduled pipeline at 5:00PM IST will run to completion. If that pipeline ran for 15 minutes, then the schedules at 5:05PM, 5:10PM, and 5:15PM will not start. The Scheduled task will make a note in its history for the instances that could not start because a previous instance was still running.