I run several jobs each day that search for files, open them, move them, etc., and I'm having a problem with jobs being automatically disabled when an error occurs, such as when a file cannot be opened or moved. The "Disable job on error" option has been deselected for all of these jobs, but the scheduler will still disable a job when it encounters an error. Is there something else that I'm missing? Please advise.

This can also happen if the job definition is incomplete. For example if a job has an email notification action setup on error but the email profile or email account property is empty.

: I run several jobs each day that search for files, open them, move them,
: etc., and I'm having a problem with jobs being automatically disabled when
: an error occurs, such as when a file cannot be opened or moved. The
: "Disable job on error" option has been deselected for all of
: these jobs, but the scheduler will still disable a job when it encounters
: an error. Is there something else that I'm missing? Please advise.

The only action I've set up to occur if an error occurs is to have a semaphore file created. This has worked just fine, but the job is still automatically disabled. Any other ideas?

: This can also happen if the job definition is incomplete. For example if a
: job has an email notification action setup on error but the email profile
: or email account property is empty.

There must be some message in the job log explaining why it happens.
By the way, what version are you running?

: The only action I've set up to occur if an error occurs is to have a
: semaphore file created. This has worked just fine, but the job is still
: automatically disabled. Any other ideas?

I'm currently running version 2.4.1 of the scheduler. This problem just occurred again during a critical process that I'm trying to create. The error that shows in the log is "An error occured while executing JAL script: Line 73: Source file 's:\IP7DTSPO.012' not found." I set the job to retry 60 seconds after an error occurs, and it did in fact restart and complete successfully 60 seconds later. Once the job was completed, however, the scheduler automatically disabled the job anyway. This can cause a major problem for me because the job needs to run every hour, and if the error occurs during the night (as it did last night at 9:00 p.m.) it will not be noticed until the next morning when someone is able to check it. And by that time, the job will have been disabled for several hours. This is a critical process that I'm trying to create and it needs to be reliable because if it doesn't run, even for a couple of hours, it can mean financial losses for the company. Is there any way that you can help me further with this? Is there something that I can do to ensure that the job will never be disabled? Any help here would be greatly appreciated.

: There must be some message in the job log explaining why it happens.
: By the way, what version are you running?

Turn off "disable on error" job property.

: I'm currently running version 2.4.1 of the scheduler. This problem just
: occurred again during a critical process that I'm trying to create. The
: error that shows in the log is "An error occured while executing JAL
: script: Line 73: Source file 's:\IP7DTSPO.012' not found." I set the
: job to retry 60 seconds after an error occurs, and it did in fact restart
: and complete successfully 60 seconds later. Once the job was completed,
: however, the scheduler automatically disabled the job anyway. This can
: cause a major problem for me because the job needs to run every hour, and
: if the error occurs during the night (as it did last night at 9:00 p.m.)
: it will not be noticed until the next morning when someone is able to
: check it. And by that time, the job will have been disabled for several
: hours. This is a critical process that I'm trying to create and it needs
: to be reliable because if it doesn't run, even for a couple of hours, it
: can mean financial losses for the company. Is there any way that you can
: help me further with this? Is there something that I can do to ensure that
: the job will never be disabled? Any help here would be greatly
: appreciated.

Send your job database file for job design verification to support@softtreetech.com

: I'm currently running version 2.4.1 of the scheduler. This problem just
: occurred again during a critical process that I'm trying to create. The
: error that shows in the log is "An error occured while executing JAL
: script: Line 73: Source file 's:\IP7DTSPO.012' not found." I set the
: job to retry 60 seconds after an error occurs, and it did in fact restart
: and complete successfully 60 seconds later. Once the job was completed,
: however, the scheduler automatically disabled the job anyway. This can
: cause a major problem for me because the job needs to run every hour, and
: if the error occurs during the night (as it did last night at 9:00 p.m.)
: it will not be noticed until the next morning when someone is able to
: check it. And by that time, the job will have been disabled for several
: hours. This is a critical process that I'm trying to create and it needs
: to be reliable because if it doesn't run, even for a couple of hours, it
: can mean financial losses for the company. Is there any way that you can
: help me further with this? Is there something that I can do to ensure that
: the job will never be disabled? Any help here would be greatly
: appreciated.

The "disable on error" property has always been turned off and it still happens. I'll send the database file to you for verification.

: Turn off "disable on error" job property.

I think I've figured it out. A message box pops up when an error occurs, and it is set to automatically close after 10 minutes. If it closes automatically after the 10-minute period, it will automatically disable the job. I believe that this is due to the fact that the "Disable" button on that pop-up form receives the focus when the form is opened. And so when the form automatically closes, the button is somehow automatically "clicked" which then disables the job. Turning off the "disable on error" property should be the thing that avoids this problem, but it doesn't. Could you look into this and see if you can fix it? Maybe the "Ignore" button should receive the focus on the pop-up form if the "disable on error" property has been turned off?

I did figure out a workaround for this by entering "0" in the "maximum message box display time" field on the "General" tab of the Tools/Options menu. That way the pop-up box doesn't pop up at all. But I'd like the option of having the message box being displayed, if possible.

: Turn off "disable on error" job property.