Skip to end of metadata
Go to start of metadata

Stopping Jobs


When you stop a job using the JOC (JobScheduler Operations Center) this job will not run any more. When you stop a running job, the task will first be ended normally and the job will be stopped.
When the stopped job is used in a job chain, all orders will wait before the node until the job will be resumed.

Jobs will be stopped, when the attribute stop_on_error=yes is set and an error occurs while the job is running.

Jobs will be stopped, when using the stop job function in JOC
Jobs remain stopped when JobScheduler will be restarted
You can only resume a stop job by using the unstop function in JOC
When you use the job in several job chains, you should set the stop on error option to false.

Disabling Jobs

A job will be disabled, by setting the enabled attribute to "no". You can do this by editing the job in joe. A disabled job only can be enabled by changing the attribute. There is no function in JOC, to dis/enable a job.

When the disabledjob is used in a job chain, all orders will wait before the node until the job will be enabled.

Jobs remain disabled when JobScheduler will be restarted
Please make sure, the the disabled job is not used in job chains.

Skipping Nodes

If you want to skip the execution of a job in a job chain, the best way to do this is to skip the node. Skipping the node has no effects to other job chains which uses the same job.

When the stopped job is used in a job chain, all orders will wait before the node until the job will be resumed.

Nodes will be skipped when using the skip node function in JOC
Jobs remain stopped when JobScheduler will be restarted
You can only resume a stopped job by using the unstop function in JOC
When you use the job in several job chains, you should set the stop on error option to false.

Write a comment…