Time Trigger in Orchestrator

[Akshaya89]

Hi all,

if the job is triggered at 9AM and the machine is not available at that time and it starts execution at 9:10 AM, and stopping condition enabled to stop the job after 30 minutes, when will the stop signal be sent?

Is it at 9:30AM? Or 9:40 AM?

Please Help..

[ashokkarale]

@Akshaya89,

The timer to stop will start when the job will get created and the job will send Stop signal at 9.30AM.

I know that’s odd but that is what it is.

[Moonlight_1712 (Anikesh Srivastav)]

If the stopping condition is set to stop the job after 30 minutes, the timer starts from the original scheduled time (i.e., when the job is triggered), not when the job actually starts running.

Some forum threads for reference:

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

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 minute…

Schedule stop after

Would like a True Stop After (the actual start time, NOT the trigger time). I can understand why some processes would need to to complete by a certain time. This is actually a Stop at 1:20 p.m. NOT a stop after. If for some reason it is hung it will Stop/Kill after x time, so that machine can be used by the next process and not tied up indefinitely. The whole purpose of scheduling is the get a bot to run… According to your documentation below, it’s merely a request the may or may not be fulfill…

[FL.Duck (James Kauczka)]

Yes, you have identified the issues.. Stop after some time is different that stop at some time post the trigger time.. It’s labeled stop after but actually stops at…
My needs/desires are not being met with this, forcing me to not be able to use that at all.. My bots must run.. To have them stop before completing makes no sense.

[sonaliaggarwal47 (Sonali Aggarwal)]

Hi @Akshaya89

if you requirement is to have a hard stop at 9.30 then you can consider one of below approaches to handle the same.

check for current time while process execution within the code, if it has reached 9.30 or around it,

1. enable shouldstop within the code.. this will trigger the job stopping and will follow a graceful shutdown approach.

2. use stop job activity but this would require you to first fetch the jobs that ar ein execution, identify your job that you want to cancel and then pass that job in this activity to stop the right job. Now this method also have an option to gracefully stop the job or kill it.

3. use stop job api call to stop the job and this will also require fetching/knowing your job id to be able to call stop job api.

Hope that helps.

Regards
Sonali