Possible bug in job log

If you create a job through the API to a Windows Master Scheduler to execute an .EXE application on a remote agent, the master records the start time for the job and records the "Finish Message Sent" with the same time/date as the start time even if the remote job takes a number of minutes to run. I am running the jobs so that only one is processed at a time so do not really understand why the end time is the same as the start time.

Nathan

That's because the process is run asynchronously. For the scheduler, in this particular mode, it just launches the process and lets it go, the job is done.

If you want it to wait for the process, please consider running it as synchronous job.

No, when I said "I am running the jobs so that only one is processed at a time" I mean Sync. If I watch the master I can see it waiting for the job to finish and when it does finish and I look at the log the end time is the same as the start time.

Nathan

I'm not quite sure how this can happen. Please post the relevant portion of schedule.log file demonstrating this issue.

Interesting, below is a copy from the log file which I now see shows the times different for the start and end but where I was looking was on the job tab for job CS131 which shows the same start and end times. I dont know if this makes any difference but the job is dynamically created? So the problem looks to be to do with the job tab displaying the wrong end time.

26/11/2009 16:07:34:744 O1 114598 CS131 Job has been disabled!
26/11/2009 16:07:34:557 O1 114598 CS131 Process finished with exit code 1
26/11/2009 16:07:34:276 O1 114598 CS131 Finish message sent.
26/11/2009 16:07:34:135 O1 114598 CS131 Job finished.
26/11/2009 16:07:33:901 O1 114598 CS131 Timeout. Process '
26/11/2009 16:04:33:76 O1 114598 CS131 Job started.