Sometimes a job come queued but the last executed of the same tipe was finished properly 15 minutes ago.
The solutions is to restart the 24x7 scheduler service.

is there a solution?

Please more information about your environment, system type and version, scheduler type and version, type of job you are running and job run-time mode (asynchronous, detached, database job, etc...)

: Sometimes a job come queued but the last executed of the same tipe was
: finished properly 15 minutes ago.
: The solutions is to restart the 24x7 scheduler service.

: is there a solution?

The 24x7 scheduler v. 3.4.26 run as a service on a Windows 2003 server with 2 GB RAM.
The job (a simple program that work on some files on the system) is NOT detached and NOT asynchronous
and is scheduled to start every 15 minutes

Do you need any other information?

Tnx

: Please more information about your environment, system type and version,
: scheduler type and version, type of job you are running and job run-time
: mode (asynchronous, detached, database job, etc...)

1. Make sure "Show job status display" option is disabled in Tools/Options menu
2. Set the job to run detached and set the job timeout to 15 minutes so that the scheduler can kill it if it takes longer then that.
3. Don't forget the restart the scheduler after you make these changes.

Hope that helps.

: The 24x7 scheduler v. 3.4.26 run as a service on a Windows 2003 server with 2
: GB RAM.
: The job (a simple program that work on some files on the system) is NOT
: detached and NOT asynchronous
: and is scheduled to start every 15 minutes

: Do you need any other information?

: Tnx

: 1. Make sure "Show job status display" option is disabled in
: Tools/Options menu

where is the "Show job status display" option? I Can't find it

: 2. Set the job to run detached

But detached requires more resources?
We have 110 jobs scheduled running on 4 agents.....are you sure that running this job detached is not a problem?

other difference betwen detached and none? i must be sure that only ONE job of the same tipe is executing in the same time.
If a job detached is running the others of the same queue will start before the first one finished?

: and set the job timeout to 15 minutes so that
: the scheduler can kill it if it takes longer then that.

But the job, if executed, finished properly (I found the end of the job on the scheduler log)

: 3. Don't forget the restart the scheduler after you make these changes.

: Hope that helps.

: where is the "Show job status display" option? I Can't find it
It is in the Tools/Options menu on the Log page

: But detached requires more resources?
Yes it needs more memory in run-time, but it ensures that jobs don't share resources with the scheduler and so cannot affect queues and scheduling engine processes.

: We have 110 jobs scheduled running on 4 agents.....are you sure that running
: this job detached is not a problem?

: other difference betwen detached and none? i must be sure that only ONE job
: of the same tipe is executing in the same time.
: If a job detached is running the others of the same queue will start before
: the first one finished?

: But the job, if executed, finished properly (I found the end of the job on
: the scheduler log)