Changes for page Jobs
Last modified by Sabrina V. on 2026/08/10 04:39
From version 14.1
edited by Sabrina V.
on 2026/06/11 06:51
on 2026/06/11 06:51
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.S V1 +XWiki.SF - Content
-
... ... @@ -21,7 +21,7 @@ 21 21 For Unix jobs, you can currently only execute Unix scripts as jobs. 22 22 23 23 {{aagon.infobox}} 24 -Please note that a working SICS connection is required to execute Unix jobs. For more info, see the section __[[Unix Scripts>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]]__.24 +Please note that a working SICS connection is required to execute Unix jobs. For more info, see the section [[Unix Scripts>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome]]. 25 25 {{/aagon.infobox}} 26 26 27 27 = Execution of jobs = ... ... @@ -186,7 +186,7 @@ 186 186 {{/aagon.infobox}} 187 187 188 188 {{aagon.versionierungsbox}} 189 -Please note that some start conditions include the option "One-time execution". In this case, the job is only executed once per client. This information is stored locally on the client. If the client drops out of the container and is reassigned, the job will not be executed again! An exception to this are Client Commands with an [[increased level>>doc:ACMP.6 9.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.Client Commands neu hinzufügen.Client Command Editor.Menüleiste.Client Command Eigenschaften .WebHome||anchor="HAllgemein-1"]]; these are executed again once.189 +Please note that some start conditions include the option "One-time execution". In this case, the job is only executed once per client. This information is stored locally on the client. If the client drops out of the container and is reassigned, the job will not be executed again! An exception to this are Client Commands with an [[increased level>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.Client Commands neu hinzufügen.Client Command Editor.Menüleiste.Client Command Eigenschaften .WebHome||anchor="HAllgemein-1"]]; these are executed again once. 190 190 {{/aagon.versionierungsbox}} 191 191 192 192 ... ... @@ -224,6 +224,11 @@ 224 224 {{/aagon.infobox}} 225 225 226 226 {{aagon.infobox}} 227 +Within the ‘Within a time period’ option, you can also select the ‘Check start condition before execution’ setting. This option ensures that a job’s start condition is checked again immediately before it is executed. The client monitors the start conditions of all known jobs. As soon as the defined start condition is met, the relevant job is added to the execution queue. 228 +However, the actual execution of the job may be delayed, for example due to jobs already running or other system activities. If the situation changes during the waiting period such that the original start condition is no longer met before the actual execution, the job will not be executed if this option is activated. 229 +{{/aagon.infobox}} 230 + 231 +{{aagon.infobox}} 227 227 In the start conditions “Start interval” and “Time window,” there is the option “Start at a random time within the time window.” We recommend that you use this start condition. This ensures that the scan data is sent to the server at different times. If a large amount of scan data is sent at the same time, the import may be delayed. 228 228 {{/aagon.infobox}} 229 229