Settings tab allows choosing how a simultaneous execution of the same Task is handled. Depending on triggering parameters and Task execution specifics, it may happen that an earlier executed instance of the Task is still running (or even only queued) when another instance is being launched.
When configuring Task's multiple instance handling, a careful consideration has to be taken on whether its structure allows for running of parallel instances or only sequential instance execution can work.
It is also possible to set Task working folder. The parameter will be used for path specification for all Actions that do not explicitly point to particular location. Task maximum run time specifies the amount of time after which the Task will be forcefully terminated.
|Task startup folder||Task working folder which will be used as a default path if not specified otherwise. Note that during Task execution the current folder can be changed by using Change Current Folder Action. If startup folder does not exist, the Warning Event 2208 will be shown.|
|Concurrency policy||Select how new instance of already running (or queued) Task will be handled. Depending on Task architecture, user can choose one of the following Task execution scenarios:
|Stop instances that run longer than||Set the maximum time limit for running an instance of the Task. Usually, the Task is stopped only when its currently performed Action completes.|
|Time units||Define and set a time frame in any given preferred format—be it milliseconds, seconds, minutes, hours or days.|
|Browse||Use Browse to select particular file or folder on local disk, network share on LAN (local area network), etc.|
- The value specified as Task startup folder parameter can be retrieved from any Action within the Task by using Task startup folder value from Task Properties group of Internal category in Variable Wizard.
Help at your fingertips…
If you have any questions, please do not hesitate to contact our support team.