Scheduling Recurring Tasks

Executing Executable Objects

Condition Symbols of Tasks

---

Restarting Executable Objects

Restarts repeat executions which have already taken place.

There are three main differences between starting and restarting an object:

1. Restarts use the real date and the logical date of the particular reference execution. The real date has the effect that the task reacts as if it is executed at the real date. The logical date affects calendar conditions.
   Because the logical date is retrieved from the reference execution, the task checks the original execution's calendar conditions.
   The real date is also retrieved from the reference execution. Among other things, it is used for calculating the earliest start time of workflow tasks. The effect is that restarted workflows do not have waiting times because of the specified earliest start time which has already been met when the original execution has taken place.
   
   
2. Restarting an object does not require the whole script to be executed. You can specify a position within the script from which processing should start. This restart point can be set in the script using the statement :RESTART. In doing so, processing steps which have already ended successfully do not have to be repeated.
   The script statement :GENERATE handles scripting blocks or individual script lines in restarts.
   
   
3. Objects that are processed by an agent always run on the computer on which the original execution has been started. The relevant information is retrieved from the statistics and therefore, it is irrelevant if the object has been modified or if agent groups are used. Workflows: Agent group agents are newly retrieved if the top workflow is restarted. If you restart subordinate workflow, the agents are assumed from the statistics if the option "Re-using agent group calculation" is activated in the workflow's Attributes tab.

You must not repeat restarted tasks because these activities are difficult to trace.

The original execution's RunID is shown in the Detail Window.

Refer to the Getting Started chapter in the Automation Engine Documentation. It describes how a restart works.

Activate the attribute dialog in the Test options tab if attributes such as the agent should be changed. Changes only apply for restarts.

Inherited object variables that are not defined in the task require the task still to be displayed in the Activity Window in order to be available for restarts.

Display

Restarts and their original executions have specific status symbols:

•   Repeated executions
•   Restarts
•   Latest restart of an execution

The following illustration shows a task with the RunID 2384085. It has been repeated twice:

Procedure

Tasks can be restarted from the Activity Window, the statistical overview or monitors:

1. Right-click the task and select the Restart command. A dialog opens in which you can make your specifications.
   
   
2. The "Restart" option is automatically checked in the Parameter tab. The Reference RunID is the running number of the task that should be repeated. By default, the field is completed with the highlighted task's RunID or with the original execution's RunID if you opted for a restart.
3. The restart point defines a point in the script from which the restart should start. The whole script is reprocessed if this field does not include a specification.
4. Select whether the start type should be kept (for example, the restart should run in the group that is defined in the object).
5. The task is not immediately restarted if you activate the Wait for manual release option. Tasks that have been started in the mode "All" via an agent group also provide the setting "Restart only aborted children". Only aborted tasks are repeated if you activate this option.
6. Select a Queue object in which the object should be restarted.
7. Additional options are available for file transfers. These options are only available if you restart the task by using the statistics.
8. Click OK. The task is immediately restarted unless the checkbox "Wait for manual release" is checked.

The "Execution with Options" command in the Explorer's context menu also opens this dialog.

 The minimum interval to be scheduled is a day. You can use the "Execution with Options" command if an object should start more often.

Script

The following script elements facilitate the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. and automated execution of restarts:

See also:

Execution with options