Stop or kill job after xx Minutes Starts counting at scheduled start time, not actual start time

Help Orchestrator
,
1

I have a number of jobs that run in the morning before anyone arrives at work. Most nights everything is fine, but occasionally a job runs long or runs away gets stuck or whatever. I just went into Orchestrator and added a Stop job after xx minutes (with Kill) with a worst case run time. So for example I have a job that is scheduled to start at 5:30AM and it normally takes 20ish minutes to run. I put the kill after 45 Minutes. So to me after the job starts if it takes longer than 45 minutes to run something went wrong and Orchestrator will kill it to allow subsequent jobs to run. That’s not what happened. While the job is scheduled to run at 5:30, previous jobs ran a bit long and it did not start until 6:02. Orchestrator killed the job at 6:15. 45 minutes after it was scheduled to start, not 45 minutes after it actually started as I would expect. Is there any setting to tell Orchestrator to start the clock at actual job start rather than scheduled start?

Thanks!

2 Likes
2

Hey @rogerfries

What I see here is you can add stop or kill the job based on the log context instead of blindly killing it since it took long time.

Hope this helps.

Thanks
#nK

3

Hi @Nithinkrishna what do you mean by log context and how would you do this.

I have been waiting for this feature which has a slightly higher traffic thread here and am a little bit dumbfounded that there isn’t massive community demand for the feature.

1 Like
4

Basically to read logs of the job understand and then kill.

5

In my case I want to blindly kill if it runs too long. There are times the process hangs and is unresponsive. I need the feature in orchestrator, and it seems like it should be easy.

1 Like
6

Hey @rogerfries

This is already available in the Orchestrator. But you need to define what is too long here so that you can use the below option.

nmnithinkrishna

Thanks
Nithin

7

For example, Let’s say I want to kill after 1 hour. The option you show will stop or kill the job 1 hour after the trigger time (the scheduled start time). Let’s say an earlier job delayed the start of this job by 50 minutes, then orchestrator will kill this job after only 10 minutes of execution time. I need an option that will kill 1 hour after the actual start time of the job.

If they added one more combo box to this Schedule ending of job execution feature to allow you to select “Scheduled Start” or “Actual Start” it would be perfect.

8

Those wanting this feature please vote to show your interest on this thread