We need to run long term execution jobs. How can we configure Client Automation so the jobs will not timeout?

Document ID : KB000025879
Last Modified Date : 14/02/2018
Show Technical Document Details

Question: 

 We need to run long term execution jobs. How can we configure Client Automation so the jobs will not timeout?

 

Environment: 

 Client automation 12.5 and above.

  

Answer: 

When users work offline and only connect to the corporate network when needed, it is not known when the scheduled jobs will be executed so a way to set a long timeout before the jobs are marked as timed out.

There are two configuration policies parameters to define the job timeout:

  • At the Manager level DSM > software delivery > Manager > "Software job options: Maximum activation time" defines the maximum number of hours for the Domain Manager to mark a job as timed out. By default is set to 168 (7 days).

  • At the Agent level DSM > software delivery > Agent > "Jobcheck: Job execution timeout" defines the maximum number of minutes a job can be executing on a target computer (Windows agents only). The value can range from 30 to 600 and is defined as 360 by default. If the timer elapses, the job status is listed as Error due to job timeout on the Domain Manager.