Signiant's job queuing feature allows users to run a set of jobs sequentially, allowing you to control and monitor job throughput and the use of network resources. Job queues are implemented through the use of Job and/or Agent Resource Controls.
You can view job queues in Administration > Resource Controls > List or in Jobs > Bandwidth/Concurrency Control. The View Job Queue option will only appear when you select a job group that has the relevant resource control applied.
The Bandwidth/Concurrency Control pages display:
Note: The default priority level for jobs is Medium.
You can only change the order of one job at a time. Jobs that are queued by an Agent resource control can also be queued by a job resource control. When both types of resource control are applied to a job, the job is first queued in the job concurrency queue. When it reaches the start of the queue and starts running, it becomes controlled by the Agent concurrency queue.
To change the order of queued jobs:
Select the progress bar for a queued job and drag it left or right to the desired position in the queue.
Note: To see all queued jobs, you can drag the zoom slider on the toolbar.
You can only add a job to a queue if the job is in a job group that has resource controls applied to it.
To add a job to a queue:
Cancelling a queued job run removes it from the queue. Cancelling a running job terminates the job, and leaves the transfer incomplete. Cancelling a queued job removes the job run from the queue and moves any remaining jobs forward in the queue. Future job runs of a scheduled job are not affected by cancelling a specific queued job run for that job. Deleting a running queued job cancels the job in mid-stream and removes all future runs of the job.
To remove a job run from a job queue:
A job will also be removed from a queue if the resource control applied to it is disabled or deleted. For more information, see Using Resource Controls.