Kill Current Job - Scheduler

orchestrator
i_considering

#1

Any disadvantages of having this option?


#2

Why would you do this?


#3

I suppose it’s the opposite of the Stop After, so if a job is stuck for whatever reason it won’t keep the next job from running. Probably only useful if you are using Specific Robots option though.

But then again, I would be scared to use it especially when I’m scheduling many jobs to run one after the other.


#4

Hello There,

I cant tell without experience :slight_smile:

Regards,
Pankaj


#5

As Clayton mentioned, just to clear off the overnight faulty jobs(if any) and have a smooth daily schedules.

Most of our processes Specific Robot as we get clearance to open ports on specific servers, so this might be use for me.

Also currently two of our Terminal Automation bots (currently in Pilot) which are scheduled to run all day won’t stop even after cycle completion. It uses Attachmate Extra session and Excel.Since stop after doesn’t work, we are killing the job EOD and it gives below error. We are still investigating this ( Killing Excel, Minimizing Logs, Checking for Argument Directions)

image

I’m not sure if below post regarding Stop After in Jobs (not Schedule) is under consideration, but this will also help.