Jobs are mostly managed by the Application Server and rarely need human interference, still there may be cases when you might want to manage jobs (or the job queue) manually. For example in an intense environment where highly prioritized jobs keep coming every second and number of simultaneously allowed jobs is low, a job with a low priority may never be executed. This means administrator should tune system performance or raise a job's priority.

Cancel jobs

All jobs in an active state can be canceled. Depending on the status the job was in when it was canceled the job will be put into another status. See table 1 for details. Jobs that are running, being paused, or paused will be aborted abruptly i.e. they do not get a chance to finish.  A user can only cancel jobs he owns. If the user has Jobs: Manage jobs permission he can cancel jobs owned by any users. Jobs with a priority of 1 cannot be canceled by any user.

Table 1: Status of jobs after cancelling

Suspending execution of new jobs

When the execution of new jobs is suspended, no jobs on the job queue (in pending state) will be executed. Jobs can still be triggered but will not be executed as long as the execution is suspended. Only users with the system permission Jobs: Manage jobs can suspend the execution of new jobs. Jobs with a priority of 1 will still be executed even if the the execution of new jobs is suspended.

Pausing and resuming of jobs

Jobs that are in running state can be paused. When a job is paused, the system will signal job's thread to pause execution. The thread will not be paused immediately but at a point in time when the thread is in some state that allows a clean interruption (which is depending on the job type).

Therefore whenever you pause a job it is put into being paused/paused state. If the job is then actually paused, i.e. the job's thread is not working any more the job is in paused state. The job is not put into paused state automatically but only if the user lists active jobs. Please also note the load balancing logic that applies for paused jobs.

A job in being paused/paused state can be resumed. The job will then immediately resume execution where he left of.

Users can  only pause jobs that they own, or if they have the system permission Jobs: Manage jobs also pause jobs of other users. Jobs with a priority of 1 cannot be paused.

Purging archived jobs

All jobs in an archived state will be kept by the system for traceability reasons. The user however has the possibility to purge jobs in archived state that are older than a specific date. To do so the user has to have the system permission Jobs: purge archived jobs.