We have approx 20 jobs using Scheduler 24x7 v.3.4.22.
Over the past week, different jobs have been getting
stuck in queue, causing all jobs starting after that
to hang in queue behind it. It is never the same job,
so isolating it to it's own queue doesn't seem
possible at this time. Last night a job started the
queueing process, yet the scheduler 24x7 status log
shows it started and finished with no problem.
Any suggestions?

Do you use single or multiple job queues?
If you use multiple, have it been happening to all queues or just one particular queue?
Do use "on finish" job notification actions and if yes, what kind?

: We have approx 20 jobs using Scheduler 24x7 v.3.4.22.
: Over the past week, different jobs have been getting
: stuck in queue, causing all jobs starting after that
: to hang in queue behind it. It is never the same job,
: so isolating it to it's own queue doesn't seem
: possible at this time. Last night a job started the
: queueing process, yet the scheduler 24x7 status log
: shows it started and finished with no problem.
: Any suggestions?

I was using a single queue,
but based on other postings I have setup queues
for different report categories.
Will see how that works going forward.
Generally use notification on error only,
and use send e-mail message if any notification is used.

: Do you use single or multiple job queues?
: If you use multiple, have it been happening to all queues or just one
: particular queue?
: Do use "on finish" job notification actions and if yes, what kind?

Best options are usually using multiple job queues and placing jobs for different applications into different job queues. This way if jobs are stuck in one queue they don't affect other queues and applications.
Now there could billions of reasons why jobs get stuck, such as network outages, file locks, resource leaking, etc... In 99% of all cases running jobs synchronous and detaches in multiple queues ensures optimal performance, application independence and solid stability. Recycling scheduling server every week or two also helps to improve overall system stability and performance.

: I was using a single queue,
: but based on other postings I have setup queues
: for different report categories.
: Will see how that works going forward.
: Generally use notification on error only,
: and use send e-mail message if any notification is used.