When I save a job the job will save and then start running. Is this normal and if so, can you turn it off?

This is a known bug that was fixed in recent versions. Please upgrade.

: When I save a job the job will save and then start running. Is this normal
: and if so, can you turn it off?

I'm running Version 3.1.0, is this the latest version?

: This is a known bug that was fixed in recent versions. Please upgrade.

Yes, this is the last one. The bug I mentioned before caused some jobs with daily schedule types and "skip late" option disabled to run after the save. Is this your case or you are dealing with something else?

: I'm running Version 3.1.0, is this the latest version?

Yes, this is probably the same problem. I've the job set to run daily with the skip late open not "on". I set this option "on" with a 10 minute delay and the log has a "skipped due to 4588 minute(s) delay. But if I change the delay to 99999 minutes the job will run when I save it.

: Yes, this is the last one. The bug I mentioned before caused some jobs with
: daily schedule types and "skip late" option disabled to run
: after the save. Is this your case or you are dealing with something else?

Do not use values over 32767 as this is the maximum supported value for the maximum delay property, just enable the skip late job options.

Some notes:
Specifying 32767 for max delay is not reasonable anyway as it is more than 22 days - a value is too large for daily jobs anyway.

In 99999 case the value is converted to a negative number that would lead to unpredictable reasults.

On save all job start times and schedules are re-initialized and so jobs with such big intervals fall into late jobs category

: Yes, this is probably the same problem. I've the job set to run daily with
: the skip late open not "on". I set this option "on"
: with a 10 minute delay and the log has a "skipped due to 4588
: minute(s) delay. But if I change the delay to 99999 minutes the job will
: run when I save it.

I do not use this option anyway, I was trying it to see if it would stop the job from running.

BTW it was set to 9999 not 99999, mistake in typing.

I set it to 3600 (1 hour) and the job ran after I saved it.

: Do not use values over 32767 as this is the maximum supported value for the
: maximum delay property, just enable the skip late job options.

: Some notes: Specifying 32767 for max delay is not reasonable anyway as it is
: more than 22 days - a value is too large for daily jobs anyway.

: In 99999 case the value is converted to a negative number that would lead to
: unpredictable reasults.

: On save all job start times and schedules are re-initialized and so jobs with
: such big intervals fall into late jobs category

This is in minutes not in seconds, so 3600 is 60 hours. Please change it 60 minutes

: I do not use this option anyway, I was trying it to see if it would stop the
: job from running.

: BTW it was set to 9999 not 99999, mistake in typing.

: I set it to 3600 (1 hour) and the job ran after I saved it.