An order job has a run time with a begin/end interval and let_run="no" (default)
If this example job is started by an order at 21:08 then it needs longer (3 min) than the end time 21:10 is reached.
- In this case the JobScheduler hangs. It means
- ... no answer per TCP
- ... no further log line.
- It seems dead but e.g. a windows service is still running
- This issue doesn't occur if let_run="yes".
- The JobScheduler doesn't hang.
- let_run doesn't have an effect for a task of a shell job which has reached the end of the run times period.
- let_run has only an effect for tasks of an api job which have multiple process steps; see http://www.sos-berlin.com/doc/en/scheduler.doc/xml/run_time.xml#attribute_let_run.
Configure the period in the job's run time with let_run="yes".